record-evidencelisted
Install: claude install-skill sson0-er/sonnede
# Recording evidence and decisions
## When to record
Write one evidence entry immediately after any of these:
- You consulted an external source: official docs, source code, an issue, an RFC.
- You ran a command to confirm behavior or a version (CLI flags, API responses, installed versions).
- You read existing code and found a fact that a design decision will rest on.
Write one decision entry whenever you choose between alternatives (adopting an approach, rejecting another).
## Writing an evidence entry
1. Create `docs/sonnede/evidence/<yyyy-mm-dd>-<slug>.md` using the format in `${CLAUDE_PLUGIN_ROOT}/templates/evidence.md`. The slug uses `[a-z0-9-]` only.
2. Body is a summary: a few lines up to a dozen. Never paste whole pages or raw command output.
3. `fetched` is today's date. `expires` is 90 days later by default, 30 days for fast-moving sources (preview features, beta APIs).
4. Separate what you learned from what you could not confirm.
5. Exclude secrets: tokens, output of authenticated commands, internal URLs, personal data.
6. Append one line to `docs/sonnede/evidence/INDEX.md`: `- <id> | <question> | expires <yyyy-mm-dd>`
## Writing a decision entry
1. Number it `<nnn>` (three digits, zero-padded) by counting existing files in `docs/sonnede/decisions/`.
2. Create `docs/sonnede/decisions/<nnn>-<slug>.md` using `${CLAUDE_PLUGIN_ROOT}/templates/decision.md`.
3. In "Rationale", reference evidence ids. If a reason has no evidence, write "unverified" next to it.
#