遵循规范驱动开发方法，生成完整的变更提案。
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionopenspec-proposal-creation-cnExecute the skills CLI command in your project's root directory to begin installation:
Fetches openspec-proposal-creation-cn from forztf/open-skilled-sdd and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate openspec-proposal-creation-cn. Access via /openspec-proposal-creation-cn in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
7
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
7
stars
遵循规范驱动开发方法，生成完整的变更提案。
创建规范提案包含三类输出：
基本流程：生成变更 ID → 脚手架目录 → 起草提案 → 编写规范差异 → 验证结构
复制此清单并跟踪进度：
规划进度:
- [ ] 第 1 步：审阅现有规范
- [ ] 第 2 步：生成唯一的变更 ID
- [ ] 第 3 步：生成目录结构
- [ ] 第 4 步：起草 proposal.md（为什么、做什么、影响摘要）
- [ ] 第 5 步：创建 tasks.json 实施清单
- [ ] 第 6 步：编写 spec-delta.md 规范差异（ADDED/MODIFIED/REMOVED）
- [ ] 第 7 步：验证提案结构
- [ ] 第 8 步：向用户展示并请求审批
在创建提案前，了解当前状态：
# 列出所有现有规范
find spec/specs -name "spec.md" -type f
# 列出进行中的变更以避免冲突
find spec/changes -maxdepth 1 -type d -not -path "*/archive"
# 搜索相关需求
grep -r "### Requirement:" spec/specs/
选择具描述性、URL 安全的标识符：
格式：add-<feature>、fix-<issue>、update-<component>、remove-<feature>
示例：
add-user-authenticationfix-payment-validationupdate-api-rate-limitsremove-legacy-endpoints校验：检查是否冲突：
ls spec/changes/ | grep -i "<proposed-id>"
按标准结构创建变更目录：
# 将 {change-id} 替换为实际 ID
mkdir -p spec/changes/{change-id}/specs/{capability-name}
示例：
mkdir -p spec/changes/add-user-auth/specs/authentication
以 templates/proposal.md 为起点。
必需章节：
语气：清晰、简洁、面向决策。避免不必要背景。
将实现拆分为具体、可测试的任务。使用 templates/tasks.json。
格式：
# 实施任务
```json
[
{
"number": 1,
"category": "阶段 1：基础设施",
"task": "环境搭建任务 - 数据库架构、依赖等",
"steps": [
{ "step": "初始化 Git 仓库并配置 .gitignore", "completed": false },
{ "step": "创建并激活 Python 虚拟环境", "completed": false },
{ "step": "创建 requirements.txt 或 pyproject.toml 并安装依赖 (FastAPI, SQLAlchemy, Pydantic, Alembic 等)", "completed": false },
{ "step": "设计初始数据库 ER 图", "completed": false },
{ "step": "配置数据库连接字符串和环境变量 (.env)", "completed": false },
{ "step": "初始化 Alembic 迁移环境", "completed": false }
],
"passes": false
}
]
**最佳实践**：
- 每个任务可独立完成
- 为每个主要组件添加测试任务
- 为每个主要组件添加测试任务
- 包含测试与验证任务
- 按依赖排序（数据库先于 API 等）
- 通常 5-15 个任务；更多时应拆分
- 每次仅处理1个step
这是最关键步骤。规范差异使用 EARS 格式（易于需求语法）。
完整 EARS 指南见 reference/EARS_FORMAT.md
差异操作：
## ADDED Requirements - 新增能力## MODIFIED Requirements - 行为变更（包含完整更新文本）## REMOVED Requirements - 弃用功能基本需求结构：
## ADDED Requirements
### Requirement: 用户登录
WHEN 用户提交有效凭据,
系统 SHALL 认证用户并创建会话。
#### Scenario: 登录成功
GIVEN 用户邮箱为 "[email protected]" 且密码为 "correct123"
WHEN 用户提交登录表单
THEN 系统创建已认证会话
AND 重定向至仪表盘
用于验证的模式见 reference/VALIDATION_PATTERNS.md
在展示给用户前运行以下检查：
结构清单：
- [ ] 目录存在：`spec/changes/{change-id}/`
- [ ] proposal.md 包含 Why/What/Impact
- [ ] tasks.json 含编号任务列表（5-15 项）
- [ ] 规范差异包含操作标题（ADDED/MODIFIED/REMOVED）
- [ ] 需求遵循 `### Requirement: <name>` 格式
- [ ] 场景使用 `#### Scenario:` 格式（四个井号）
自动化检查：
# 统计差异操作（应 > 0）
grep -c "## ADDED\|MODIFIED\|REMOVED" spec/changes/{change-id}/specs/**/*.md
# 验证场景格式（显示行号）
grep -n "#### Scenario:" spec/changes/{change-id}/specs/**/*.md
# 检查需求标题
grep -n "### Requirement:" spec/changes/{change-id}/specs/**/*.md
清晰总结提案：
## Proposal Summary
**Change ID**：{change-id}
**Scope**：{简要描述}
**创建的文件**：
- spec/changes/{change-id}/proposal.md
- spec/changes/{change-id}/tasks.json
- spec/changes/{change-id}/specs/{capability}/spec-delta.md
**下一步**：
请评审提案。如认可或修正后，请回复 "openspec开发" 或 "按顺序完成任务" 开始实施。
EARS 格式细节：见 reference/EARS_FORMAT.md 验证模式：见 reference/VALIDATION_PATTERNS.md 完整示例：见 reference/EXAMPLES.md
新增能力时：
ADDED Requirements 差异修改既有行为时：
MODIFIED Requirements 差异移除功能时：
REMOVED Requirements 差异不要：
要：
所有模板位于 templates/ 目录：
Token 预算：此 SKILL.md 约 250 行，低于建议的 500 行上限。引用文件按需加载以逐步呈现。
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
openspec-proposal-creation-cn is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
We added openspec-proposal-creation-cn from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in openspec-proposal-creation-cn — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend openspec-proposal-creation-cn for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
openspec-proposal-creation-cn fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Keeps context tight: openspec-proposal-creation-cn is the kind of skill you can hand to a new teammate without a long onboarding doc.
openspec-proposal-creation-cn reduced setup friction for our internal harness; good balance of opinion and flexibility.
openspec-proposal-creation-cn is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Solid pick for teams standardizing on skills: openspec-proposal-creation-cn is focused, and the summary matches what you get after install.
openspec-proposal-creation-cn has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 60