// Archives a completed OpenSpec change and updates the main specifications. Use when implementation is finished and verified.
Staff Strategic Orchestrator for Spec-Driven Development (SDD). Proactively leads the lifecycle of a change, ensuring strategic alignment, technical rigor, and cross-disciplinary excellence.
Outputs enriched instructions for creating an artifact or applying tasks for an OpenSpec change. Use when the agent needs guidance on how to write a spec, design, or implement tasks.
Displays the completion status of artifacts for an OpenSpec change. Use to track progress of proposal, specs, design, and tasks.
Creates a new OpenSpec change directory and initial structure. Use when starting a new feature, bugfix, or refactor.
Initializes OpenSpec in a project directory. Use when starting a new project or adding OpenSpec to an existing one.
Lists OpenSpec items such as active change proposals and specifications. Use to discover what changes are in progress or what specs exist.
| name | archiving-openspec-change |
| description | Archives a completed OpenSpec change and updates the main specifications. Use when implementation is finished and verified. |
Finalizes a change proposal by moving its artifacts to the archive and incorporating the new requirements and scenarios into the project's main specifications.
npx @fission-ai/openspec@latest archive --help.checking-openspec-status and validating-openspec-items before archiving.npx @fission-ai/openspec@latest archive <change-name>.-y to skip confirmation prompts if you are confident:
npx @fission-ai/openspec@latest archive <change-name> -y--skip-specs:
npx @fission-ai/openspec@latest archive <change-name> --skip-specs--no-validate only if absolutely necessary and you understand the risks.Command: npx @fission-ai/openspec@latest archive add-login -y
Expected Output: The add-login change is moved to the archive, and main specs are updated.