OpenSpec Archive Skill
When to Invoke
Automatically activate when user:
- Says "Archive this change", "Close the change", "Finalize change"
- Asks "Document this change", "Mark as complete", "Archive proposal [X]"
- Has completed an OpenSpec change that needs closure
- Mentions "archive", "close", "document", "finalize" with change context
- Uses words like: archive, close, document, finalize, complete, wrap up
Specific trigger phrases:
- "Archive this change"
- "Close change [proposal-id]"
- "Document the change"
- "Finalize the implementation"
- "Mark proposal [X] as complete"
- "Wrap up this change"
Prerequisites:
- OpenSpec change has been implemented
- Tests pass and validation is complete
- Deployment or rollout is done (or documented)
Do NOT invoke when:
- Change not yet implemented (use openspec-change-implementation)
- Tests failing or validation incomplete
- Missing approvals or sign-offs
- Change still in progress
Auto-document:
- Learnings and deviations
- Metrics (time, lines changed, tests added)
- Follow-up tasks if any
Mission
Document the outcome of Level 0-1 work, ensuring artifacts, approvals, and follow-up actions are captured before closing the OpenSpec workflow.
Inputs Required
- proposal: original proposal.md with approvals
- implementation_log: execution notes or commits from implement skill
- validation_evidence: test results or reviewer feedback
Outputs
- Archive summary (
archive.md) with outcomes, metrics, and learnings (template: assets/archive-template.md.template)
- Updated proposal/tasks reflecting completion status
- Deployment or rollback notes stored with project documentation
- Canonical specs in
openspec/specs/ synchronized with approved deltas
scripts/archive_change.py copies validated spec deltas from openspec/changes/<change-id>/specs/ into openspec/specs/.
Process
- Verify closure conditions using
CHECKLIST.md.
- Gather final state: what shipped, what remains, and any deviations.
- Record metrics, approvals, and validation evidence in
archive.md.
- Run
scripts/archive_change.py <change-id> to merge spec deltas into openspec/specs/.
- Capture learnings and recommended follow-up actions, then update artifacts and communicate closure.
Quality Gates
All checklist items must pass before marking work as archived.
Error Handling
- If validation evidence or approvals are missing, request them before closing.
- Surface outstanding tasks and assign owners if work cannot be fully archived.
1---2name: openspec-change-closure3description: Archives completed L0-1 changes.4---5
6# OpenSpec Archive Skill
7
8## When to Invoke
9
10**Automatically activate when user:**
11- Says "Archive this change", "Close the change", "Finalize change"
12- Asks "Document this change", "Mark as complete", "Archive proposal [X]"
13- Has completed an OpenSpec change that needs closure
14- Mentions "archive", "close", "document", "finalize" with change context
15- Uses words like: archive, close, document, finalize, complete, wrap up
16
17**Specific trigger phrases:**
18- "Archive this change"
19- "Close change [proposal-id]"
20- "Document the change"
21- "Finalize the implementation"
22- "Mark proposal [X] as complete"
23- "Wrap up this change"
24
25**Prerequisites:**
26- OpenSpec change has been implemented
27- Tests pass and validation is complete
28- Deployment or rollout is done (or documented)
29
30**Do NOT invoke when:**
31- Change not yet implemented (use openspec-change-implementation)
32- Tests failing or validation incomplete
33- Missing approvals or sign-offs
34- Change still in progress
35
36**Auto-document:**
37- Learnings and deviations
38- Metrics (time, lines changed, tests added)
39- Follow-up tasks if any
40
41## Mission
42Document the outcome of Level 0-1 work, ensuring artifacts, approvals, and follow-up actions are captured before closing the OpenSpec workflow.
43
44## Inputs Required
45- proposal: original proposal.md with approvals
46- implementation_log: execution notes or commits from implement skill
47- validation_evidence: test results or reviewer feedback
48
49## Outputs
50- Archive summary (`archive.md`) with outcomes, metrics, and learnings (template: `assets/archive-template.md.template`)
51- Updated proposal/tasks reflecting completion status
52- Deployment or rollback notes stored with project documentation
53- Canonical specs in `openspec/specs/` synchronized with approved deltas
54
55`scripts/archive_change.py` copies validated spec deltas from `openspec/changes/<change-id>/specs/` into `openspec/specs/`.
56
57## Process
581. Verify closure conditions using `CHECKLIST.md`.
592. Gather final state: what shipped, what remains, and any deviations.
603. Record metrics, approvals, and validation evidence in `archive.md`.
614. Run `scripts/archive_change.py <change-id>` to merge spec deltas into `openspec/specs/`.
625. Capture learnings and recommended follow-up actions, then update artifacts and communicate closure.
63
64## Quality Gates
65All checklist items must pass before marking work as archived.
66
67## Error Handling
68- If validation evidence or approvals are missing, request them before closing.
69- Surface outstanding tasks and assign owners if work cannot be fully archived.
majiayu000