From specclaw
Archives completed changes to .specclaw/changes/archive/ with date prefix, closes GitHub issues, and optionally creates git tags.
How this skill is triggered — by the user, by Claude, or both
Slash command
/specclaw:archiveThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**First, run** `specclaw-ensure-init .specclaw` — idempotently creates `.specclaw/` if it doesn't exist (silent if already initialized; auto-inits using the current directory's basename as the project name).
First, run specclaw-ensure-init .specclaw — idempotently creates .specclaw/ if it doesn't exist (silent if already initialized; auto-inits using the current directory's basename as the project name).
Archive a completed change.
specclaw-validate-change .specclaw <change> archive. If it fails, report and stop..specclaw/changes/archive/YYYY-MM-DD-<change>/.specclaw-update-status .specclaw.specclaw-gh-sync close .specclaw <change> to close the issue.azdo.boards.sync: true): specclaw-azdo-issue close .specclaw <change> to post a closing comment and add a closed-by-specclaw tag. (Does not transition Work Item state — humans drive state in ADO.)npx claudepluginhub chan4lk/specclaw --plugin specclawArchives a completed change in the openspec experimental workflow, checking artifact and task completion, and optionally syncing delta specs before archiving.
Archives a completed change: gates on task completion, syncs delta into main specs, freezes change directory, and revalidates all specs.
Archives a closed issue's requirements, architecture, and review docs from specs/ into the GitHub wiki. Use when a finished issue's working artifacts should be retired.