vaultspec-writelisted

Write an implementation plan of waves, phases, and steps. Use only after the authorizing ADR - or the cluster of ADRs a roll-up plan executes - is approved.
nevenincs/vaultspec-rag · ★ 1 · AI & Automation · score 67

Install: claude install-skill nevenincs/vaultspec-rag

# Plan writing skill (vaultspec-write) Use this skill: - To write the required implementation plan grounded with research and ADRs. - To plan **non-trivial work, such as new features, complex auditing, or refactoring**. - When the user explicitly asked to "write plan" or "draft Steps". This skill **MUST always** be called after `vaultspec-adr` concludes with architectural approval. **Announce at start:** "I'm using the `vaultspec-write` skill to write the implementation plan." ## Important - If part of the `vaultspec-research` -> `vaultspec-adr` flow, this skill **MUST** be provided with the relevant Research and ADR documents. - If invoked standalone, you must locate or request relevant context. ## CLI usage mandate Plan documents authored by this skill MUST be manipulated via the `vaultspec-core vault plan` CLI rather than by hand-editing the markdown body. The CLI is the canonical surface for every identifier-affecting change. The verbs are: - `vaultspec-core vault plan step add | insert | edit | move | remove` - `vaultspec-core vault plan step check | uncheck | toggle` (state) - `vaultspec-core vault plan phase add | insert | edit | move | renumber | remove` - `vaultspec-core vault plan wave add | insert | edit | move | remove` - `vaultspec-core vault plan epic intent show | edit` (L4 only) - `vaultspec-core vault plan tier show | promote | demote` The CLI guarantees canonical-identifier preservation, gap-no-reuse via a hidden retirement ledger, and display-p