Use this skill at Step 3 of the v2 SOP to create the OpenSpec change scaffold (proposal.md / design.md / specs/ / tasks.md) for a stage of the PRD. Initializes the change directory under openspec/changes/<slug>/, fills the proposal with PRD references, and emits a design.md skeleton including a Compliance Design section that links to COMPLIANCE_TAG.md. After this skill, use openspec-continue-change for full content expansion. Chinese trigger examples: "新建 OpenSpec change", "Step 3", "OpenSpec 初始化", "建 change", "新建变更". Do NOT use without a signed COMPLIANCE_TAG (Step 0) and a clean PRD (Step 1) and aligned TDD (Step 2). Success = change directory exists with valid skeleton, all references resolve, no orphan spec ids.
How to install openspec-new-change?
charliehzm/medharness/openspec-new-change
$npx -y skills add charliehzm/medharness --skill openspec-new-changeInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Run `npx skills use "https://github.com/charliehzm/medharness" --skill "charliehzm/medharness/openspec-new-change"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/charliehzm/medharness" that are relevant to the current task. Run `npx skills add "https://github.com/charliehzm/medharness"` and select the relevant skills, then follow their instructions.
Related
6 picksType
- improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.Jul 2026
- domain-modelingBuild and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision,…Jul 2026
- caveman-reviewUltra-compressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix.Jul 2026
- codebase-designShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a…Jul 2026
- code-reviewReview the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding…Jul 2026
- resolving-merge-conflictsUse when you need to resolve an in-progress git merge/rebase conflict.Jul 2026
