Research (vaultspec-research)
Produces a Research record: the evidence a later ADR decides on. Enter it when the
vaultspec decision test warrants an ADR and the options are not already weighed in the
vault or the code. A question this session can answer without new evidence is answered
in the conversation. Reuse sufficient existing Research, Reference, or Audit evidence
before creating more. This skill terminates within one run.
Steps
- Ground per the
vaultspec-discovery rule, decisions first: prior ADRs and research on
the feature, read whole. Link what already exists; do not restate it.
- Scaffold:
vaultspec-core vault add research --feature {feature} (or the create
tool). Read .vaultspec/templates/research.md; its hint blocks fix the body shape:
answer-first lead, claim-first ## Findings, closing ## Sources.
- Research in this run, or dispatch the
vaultspec-adr-researcher persona (and
vaultspec-researcher for parallel threads) with "Conduct research on {topic}", and
transfer the returned findings into the body without diluting their locators.
- When the decision needs grounding in real code, branch to
vaultspec-code-research
for a Reference record and link it in related:.
- Fill every section this session; never leave or present an unfilled record.
- Verify with
vaultspec-core vault check all.
Quality gate
Judged by decision value per token; later phases re-read this record.
- Answer-first. The lead states question, stakes, and conclusion; each finding opens
with its claim.
- Locator-anchored. Every non-obvious claim carries a re-fetchable locator (URL,
file:line, commit SHA, package@version, RFC); an unanchored claim is marked as
opinion.
- Comparative and specific. Alternatives named with why each was kept or rejected;
versions, dates, and numbers pinned.
- Grounding, not deciding. At most name the option the evidence favours and what the
ADR must settle. Decisions are recorded only in the ADR.
- Bounded and lean. Uninvestigated areas stated; link, do not copy; no hedging, no
restated prompt, no closing summary.
Next
Proceed to vaultspec-adr, in this run or the next; the ADR's approval covers the
findings, so this record needs no reply of its own. If the user faults the findings,
revise this record's body in place.
1---2name: vaultspec-research3description: Ground a decision in evidence before it is made. Use when an ADR is warranted and the options have not been weighed on evidence already in the vault or the code.4---56# Research (vaultspec-research)78Produces a Research record: the evidence a later ADR decides on. Enter it when the9vaultspec decision test warrants an ADR and the options are not already weighed in the10vault or the code. A question this session can answer without new evidence is answered11in the conversation. Reuse sufficient existing Research, Reference, or Audit evidence12before creating more. This skill terminates within one run.1314## Steps1516- Ground per the `vaultspec-discovery` rule, decisions first: prior ADRs and research on17 the feature, read whole. Link what already exists; do not restate it.18- Scaffold: `vaultspec-core vault add research --feature {feature}` (or the `create`19 tool). Read `.vaultspec/templates/research.md`; its hint blocks fix the body shape:20 answer-first lead, claim-first `## Findings`, closing `## Sources`.21- Research in this run, or dispatch the `vaultspec-adr-researcher` persona (and22 `vaultspec-researcher` for parallel threads) with "Conduct research on `{topic}`", and23 transfer the returned findings into the body without diluting their locators.24- When the decision needs grounding in real code, branch to `vaultspec-code-research`25 for a Reference record and link it in `related:`.26- Fill every section this session; never leave or present an unfilled record.27- Verify with `vaultspec-core vault check all`.2829## Quality gate3031Judged by decision value per token; later phases re-read this record.3233- **Answer-first.** The lead states question, stakes, and conclusion; each finding opens34 with its claim.35- **Locator-anchored.** Every non-obvious claim carries a re-fetchable locator (URL,36 `file:line`, commit SHA, `package@version`, RFC); an unanchored claim is marked as37 opinion.38- **Comparative and specific.** Alternatives named with why each was kept or rejected;39 versions, dates, and numbers pinned.40- **Grounding, not deciding.** At most name the option the evidence favours and what the41 ADR must settle. Decisions are recorded only in the ADR.42- **Bounded and lean.** Uninvestigated areas stated; link, do not copy; no hedging, no43 restated prompt, no closing summary.4445## Next4647Proceed to `vaultspec-adr`, in this run or the next; the ADR's approval covers the48findings, so this record needs no reply of its own. If the user faults the findings,49revise this record's body in place.
nevenincs