openspec-new-change
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
Profile →npx skills add charliehzm/medharness --skill openspec-new-change --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# OpenSpec New Change The bootstrap step of an OpenSpec change. Sets up structure; content fills in the next step (`openspec-continue-change`). ## Scaffolded structure ``` openspec/changes/<slug>/ ├── proposal.md # 30-second readout: why + scope + stage + DoD ├── design.md # technical approach + 合规设计说明 ├── specs/ │ └── index.md # spec id table; one row per shippable behavior ├── tasks.md # task li
What does the openspec-new-change skill do?
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
How do I install it?
Run `npx skills add charliehzm/medharness --skill openspec-new-change --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From charliehzm/medharness, a repository with 96 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.