Archive completed change proposals from docs/changes/ to docs/_archive/ after verifying preconditions.
Archive completed change proposals from docs/changes/ to docs/_archive/<YYYY-MM>/.
dev-workflow skillAll of the following must be true before archiving:
| # | Condition | How to Verify |
|---|---|---|
| 1 | Implementation complete | All checklist items in the change doc are done |
| 2 | Build and tests pass | Run the project's build and test commands |
| 3 | Code review approved | PR has been approved |
| 4 | Branch merged | Feature branch merged into target branch |
| 5 |
| Module specs updated |
Related specs in docs/modules/ reflect any contract changes |
If conditions are not met, report what is missing and suggest completing those first.
If the user specifies a change, locate it. Otherwise, list changes in docs/changes/ with status Implemented for the user to choose.
Check each precondition:
git branch --merged)Present a summary:
Archive check: YYYY-MM-DD-<slug>
Tasks: N/N complete
Branch: merged into main
Module specs: updated / needs sync
Tests/review: user confirmation required
Proceed?
After confirmation:
docs/_archive/<YYYY-MM>/ if it does not existdocs/changes/YYYY-MM-DD-<slug>/ to docs/_archive/<YYYY-MM>/<slug>/docs/_archive/README.mdBranch and worktree cleanup are out of scope for this skill — leave them to the user.
If multiple changes are ready, list them all and let the user select which to archive.