vaultspec-adrlisted

# ADR writing skill (vaultspec-adr) Use this skill: - After a `vaultspec-research` session has concluded with a recommendation. - When multiple competing technical choices need a grounding document. - When a significant architectural decision is made that affects the project's foundations, feature set, or development trajectory. - To document the blast radius, "why", and "what" of major architectural choices. - When an accepted decision needs refining or concretizing - this amends the existing record in place, not a new document (see Amend or supersede). **Announce at start:** "I'm using the `vaultspec-adr` skill to create a new ADR." ## Required steps - **Ground the decision in existing intent first.** Before drafting, retrieve the prior decisions that bind this area - the surest way to architect on top of them rather than silently contradicting them. Lead with `vaultspec-rag search "<intent>" --type vault --doc-type adr` (the directed ADR filter, sharper than catch-all `--type vault`); read each in full - a record already governing this scope routes through Amend or supersede below. Use `vaultspec-rag search "<intent>" --type code` for the implementation sites the decision will touch, then confirm exact symbols with grep, and lean on `vaultspec-core status` and `vaultspec-core vault list` - first-class for orientation \- to map related records. Round out decision recall by listing `.vault/adr/` and filtering by feature - search can miss lower-ra