change-manager

---

name: change-manager description: Used when the user adds a feature or incrementally changes an existing project that already has Product-Spec.md. Runs the changes/ workflow (propose, apply, verify, archive), aligned with OpenSpec-style SDD while delegating implementation to dev-planner and dev-builder. version: 1.1.0 updated: 2026-05-26 requires: []

[Task] Orchestrate one named change under changes/<change-name>/ from proposal through archive. Do not replace product-spec-builder for greenfield projects or wholesale Spec rewrites — use this Skill for brownfield, scoped deltas.

[Not For] - First-time Product-Spec from scratch -> use /product-spec-builder instead - Whole Spec rewrite (major iteration, no single feature scope) -> use /product-spec-builder iteration mode on Product-Spec.md directly - Bug fixes only -> use /bug-fixer instead - Release packaging -> use /release-builder instead

[Dependency Check] Required: - Product-Spec.md -> if missing, prompt to call /product-spec-builder first - Project has or will have changes/ directory (create on first propose if absent)

Optional:
- DEV-PLAN.md -> apply phase may update or add Phases scoped to this change
- Design-Brief.md / design MCP -> fill design.md when UI is involved
- Existing `changes/<other>/` -> warn if another change folder is in progress without archive

[First Principles] → references/first-principles.md

[OpenSpec + Superpowers Handoff] → references/openspec-handoff.md

[Output Style] → references/output-style.md → 每 Phase（propose/apply/verify/archive）完成后必须附加 ../_shared/output-status-protocol.md

[File Structure] change-manager/ ├── SKILL.md ├── commands/change-manager.md ├── references/ │ ├── first-principles.md │ ├── openspec-handoff.md │ ├── output-style.md │ ├── change-assessment-checklist.md │ ├── anti-rationalization.md │ ├── anti-ai-slop-checklist.md │ └── workflow.md # propose → apply → verify → archive └── templates/ ├── change-proposal-template.md ├── change-specs-template.md ├── change-design-template.md ├── change-tasks-template.md └── change-verify-template.md

[Gotchas] Skipping propose: "Just code it" -> still create minimal proposal.md + specs.md so archive and review have a baseline. product-spec-builder overlap: Do not let product-spec-builder create changes/ — only this skill creates that folder. It may still edit Product-Spec.md during propose when merging requirements. Orphan changes/: Folders left un-archived for weeks -> list active changes on session start; nag to verify or archive. Spec drift: Merging specs.md into Product-Spec.md twice or not at all -> archive checklist must include CHANGELOG + Spec section update. Whole-repo dev-builder: apply must pass change scope (files/tasks from changes// only), not entire DEV-PLAN backlog.

[Anti-Rationalization Checklist] → references/anti-rationalization.md 迭代过程中遇阻力时读取：识别跳过 propose/verify/archive 环节的常见借口。

[Output Artifacts] - changes/<change-name>/proposal.md - changes/<change-name>/specs.md - changes/<change-name>/design.md - changes/<change-name>/tasks.md - changes/<change-name>/verify.md (after verify phase) - changes/archive/<change-name>/ (after archive)