openspec-proposal-creation-cn
A framework for creating structured change proposals and specification differences using the OpenSpec method. It guides users through generating proposal documents, implementation task lists, and requirement changes using EARS syntax.
Is openspec-proposal-creation-cn safe to install?
Review before installing: our audit of openspec-proposal-creation-cn's source files found 8 shell commands, 0 external URLs, file reads and writes (medium risk). Every command and URL listed appears verbatim in the skill's source. The skill performs file system operations including directory creation and file reading/writing within the local repository structure. It also executes shell commands to search and validate files.
How we audit skills: our security review methodology.
Who is this skill for?
Software developers, system architects, and technical leads who manage project requirements and development workflows.
What can you do with it?
- Planning new features or capabilities
- Creating structured change proposals
- Writing formal specification differences
- Managing development workflows through task lists
- Validating proposal structures before implementation
How good is this skill?
Quality score: 9/10. The skill provides a clear, structured, and repeatable process for technical documentation. It includes specific bash commands for validation and follows a logical workflow. The documentation is comprehensive.
What does the skill file contain?
# 规范提案创建 遵循规范驱动开发方法，生成完整的变更提案。 ## 快速开始 创建规范提案包含三类输出： 1. **proposal.md** - 为什么、做什么、影响摘要 2. **tasks.json** - 编号的实施清单 3. **spec-delta.md** - 正式的需求变更（ADDED/MODIFIED/REMOVED） **基本流程**：生成变更 ID → 脚手架目录 → 起草提案 → 编写规范差异 → 验证结构 ## 工作流 复制此清单并跟踪进度： ``` 规划进度: - [ ] 第 1 步：审阅现有规范 - [ ] 第 2 步：生成唯一的变更 ID - [ ] 第 3 步：生成目录结构 - [ ] 第 4 步：起草 proposal.md（为什么、做什么、影响摘要） - [ ] 第 5 步：创建 tasks.json 实施清单 - [ ] 第 6 步：编写 spec-delta.md 规范差异（ADDED/MODIFIED/REMOVED） - [ ] 第 7 步：验证提案结构 - [ ] 第 8 步：向用户展示并请求审批 ``` ### 第 1 步：审阅现有规范 在创建提案前，了解当前状态： ```bash # 列出所有现有规范 find spec/specs -name "spec.md" -type f # 列出进行中的变更以避免冲...
Frequently asked questions
What is the EARS format?
EARS (Easy Approach to Requirements Syntax) is a structured method for writing requirements, focusing on clarity and testability. The skill uses it to define ADDED, MODIFIED, and REMOVED requirements.
How does the skill ensure proposal consistency?
The skill provides a checklist and automated bash commands to verify the directory structure, the presence of required sections in proposal.md, and the correct formatting of requirements and scenarios.
Can I use this for breaking changes?
Yes. The skill includes a specific pattern for breaking changes, requiring the use of MODIFIED Requirements, updated requirement text, and migration tasks in the tasks.json file.
Related skills
content-strategy
86.4KContent marketers, founders, and marketing teams planning content roadmaps and editorial calendars
The content-strategy skill assists users in planning content strategies, identifying topics, and building editorial calendars. It guides users through gathering business context, researching customers, analyzing competitors, and mapping content to the buyer's journey. It provides frameworks for searchable and shareable content, pillar identification, and topic clustering.
gws-workflow-email-to-task
17.9KUsers who manage tasks directly from their Gmail inbox via the command line
The gws-workflow-email-to-task skill converts a Gmail message into a Google Tasks entry using the gws CLI tool.
product-marketing
17.6KProduct managers, marketers, and founders who want to centralize their product positioning and audience information for AI-assisted marketing tasks
This skill creates and maintains a product marketing context document at .agents/product-marketing.md. It helps users define product positioning, target audiences, and messaging to ensure consistency across other marketing tasks.
meeting-minutes
9.2KTeams and individuals who need to document internal syncs, standups, design reviews, and planning meetings efficiently
The meeting-minutes skill generates structured, actionable meeting minutes from transcripts, recordings, or raw notes for internal meetings lasting 60 minutes or less. It enforces a strict schema that captures metadata, attendance, decisions, and action items with owners and due dates.