vaultspec-researchlisted

# Research and brainstorm skill (vaultspec-research) Use this skill: - Before implementing non-trivial features. - When unsure about major design decisions. - Before refactors with unclear scope. - Before debugging complex issues. - When you need user input on design options. **Announce at start:** "I'm using the `vaultspec-research` skill to conduct structured research and brainstorming." ## Required steps - **Ground in existing intent first.** Begin by grounding via semantic search - the fastest, cheapest way to surface what the project already decided and built. Follow the validated sequence: locate, read whole, confirm. Retrieve governing decisions with `vaultspec-rag search "<intent>" --type vault --doc-type adr` (the directed ADR filter, sharper than catch-all `--type vault`), prior exploration with `vaultspec-rag search "<intent>" --type vault` (or `--doc-type research`), and the implementation sites with `vaultspec-rag search "<intent>" --type code`. Lean on `vaultspec-core status` and `vaultspec-core vault list` - first-class for orientation \- to map in-flight plans and records. Read what this surfaces in full and check for overlap before adding new findings; round out decision recall by listing `.vault/adr/` and filtering by feature. Where `vaultspec-rag` is not installed, the `vaultspec-core` discovery verbs and grep carry the same sequence. - **Read and use the template** at `.vaultspec/templates/research.md`; its embedded hint block