skills/archive/SKILL.md
Archive consumed blueprint artifacts. Moves artifacts to archive/ and stores content in git notes. Triggers: 'archive', 'archive blueprint', 'clean up blueprints', 'done with this spec/plan/review'.
npx skillsauth add luan/dot-claude archiveInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Move consumed blueprint artifacts to archive/ and store their content as git notes for long-term retrieval.
<slug-or-path> — file path or slug substring to match--type <spec|plan|review|report> — restrict search to one artifact type (optional)List active artifacts:
ct spec list --all
ct plan list --all
ct review list --all
ct report list --all
Present the combined list and ask which to archive via AskUserQuestion.
Search for matching artifact across types (or filtered by --type):
# Try each type, find file whose name contains the slug
fd "<slug>" ~/blueprints/ --type f --extension md --exclude archive
If exactly one match → archive it. Multiple matches → present choices. No match → report and stop.
Prefer the MCP blueprint_archive tool ({ stem, kind? }). It moves the file to ~/blueprints/<project>/archive/, stores content as a git note, and commits+pushes.
CLI equivalent, useful for batch archival or previewing:
ct <type> archive <file-path> # single
ct <type> archive --batch <f1> <f2> <f3> # one commit for all
ct <type> archive --dry-run --batch <f1> <f2> # preview, no writes
Report what was archived.
tools
Tree-sitter indexed code navigator (ct sym CLI). Use INSTEAD OF Read/Grep/Glob/Bash when exploring existing code, understanding how something works, locating a symbol, tracing the call graph up (impact) or down (trace), finding implementations of an interface, scoping a diff to one symbol, or preparing to edit code you have not read yet. Triggers: 'how does X work', 'explain this class/file/symbol', 'walk me through X', 'what does X do', 'where is X defined', 'who calls X', 'what does X call', 'find implementations of', 'what breaks if I change X', 'outline this file', 'map imports', 'show me this symbol', exploring unfamiliar repo, tracing call graph, scoping diff to a symbol, preparing to edit code I haven't read, about to Read a file over ~500 lines to understand it. Do NOT use for: writing new code from scratch, editing prose or config, running tests, or when a stack trace already names the file and line.
development
Fully autonomous development workflow from prompt to commit. Chains spec → develop → review → commit. Triggers: /vibe, 'vibe this', 'autonomous workflow', 'just do it all', 'build this end-to-end', 'full pipeline', 'handle everything'.
development
Comprehensive vault maintenance — cross-references blueprints against codebase state to produce a maintenance plan: archive consumed artifacts, audit docs for staleness, propose new docs for undocumented stable systems. Triggers: 'vault sweep', 'sweep the vault', 'clean up vault', 'vault maintenance', 'what can we archive', 'audit blueprints', 'vault hygiene', 'blueprint cleanup'. Use whenever the user wants a holistic view of vault health rather than archiving a single artifact (that's /archive). Also use when the user asks what's stale, what needs docs, or whether artifacts can be cleaned up.
development
Analyze current diff, classify changes by risk, and produce structured manual test plan. Triggers: 'test plan', 'what should I test', 'manual testing', 'verification steps', 'QA checklist'. Exits early for trivial changes. Do NOT use when: writing automated tests — use /develop with TDD. Do NOT use when: reviewing code quality — use /crit instead.