| name | sdc-archive |
| description | Use when a completed SDC change is ready for archival and durable knowledge compaction. |
Codex/Hermes workflow skill generated from commands/archive.md.
Treat the user's current request as $ARGUMENTS. In Codex/Hermes, route to the matching SDC skill/workflow instead of expecting /sdc:* slash-command support.
SDC Archive
Use "$ARGUMENTS" as the change id. Archive only after required checks pass or equivalent evidence exists.
During archive, run the Knowledge Compact Gate. Required spec/archive writes may proceed; optional updates to common-ground.md, expert-routing.md, decisions, standards, reports, AGENTS.md, project.md, or project-cognition.md require explicit user confirmation before writing.
This also applies to optional product knowledge, technical knowledge, and memory updates.
Run the SDC archive workflow:
- Require a final confirmed spec, completed tasks, traceability, and check evidence.
- Promote the final spec to
.sdc/specs/<change-id>.md.
- Create or update
archive.md with conclusion, evidence, residual risks, coverage summary, and Knowledge Compact Gate.
- Preserve Artifact Output Contract coverage in archive evidence, including required diagrams/contracts/matrices/checklists and any N/A reasons.
- Evaluate
knowledge-candidates.md, Common Ground drift, and expert routing drift; recommend which candidates should be promoted to .sdc/common-ground.md, .sdc/expert-routing.md, .sdc/knowledge/product/, .sdc/knowledge/technical/, .sdc/memory/, .sdc/decisions/, .sdc/standards/, or AGENTS.md.
- Move the completed change into
.sdc/changes/archive/<change-id>/.
- Never delete change history or silently overwrite an existing stable spec.