vaultspec-core
Run a feature from research to reviewLink to Run a feature from research to review
The ordinary workflow is three prompts and two approval decisions. Replace search-api with one feature tag throughout.
Research and decideLink to Research and decide
Use vaultspec-research to investigate adding full-text search to the API. Use the feature tag search-api.
Read the evidence and alternatives. Ask for corrections or approve the research and architecture decision. Do not approve an ADR that leaves a requirement unresolved.
Approve and execute the planLink to Approve and execute the plan
Read the proposed plan. Check its scope, ordering, and verification. Approve it, then ask:
Execute the approved plan for search-api.
Check progress without changing the vault:
Command
vaultspec-core status search-api
ReviewLink to Review
Use vaultspec-code-review to review the completed search-api implementation.
Read the audit with the final code diff. Resolve blocking findings before accepting the feature. Record checks validate structure and links; they do not prove correctness or require an audit.
Manual and advanced operationLink to Manual and advanced operation
Use the vaultspec-core CLI reference to create records, edit plan structure, resolve branch collisions, rename or archive features, and automate checks. Use review guidance for the correctness gate.
For commit and continuous-integration gates, use the Core check command reference.
Where to go nextLink to Where to go next
How Vaultspec works - the records each stage writes and who approves them.
Driving the vault from the command line - the same operations without an agent.
Reaching Vaultspec from your agent - the same operations over MCP.