# Record Evidence

> Use when a delivery run dispatches a durable-recording action: filing the debugging trail (record_debugging_evidence), filing the knowledge-maintenance pass's evidence (record_maintenance_evidence), or recording the run's final outcome and status update (record_outcome) — all documentation-steward work. One shared procedure — file it where the next reader will look, link rather than restate, update state and evidence in the same change set — parameterized by the action id passed as the first skill argument. Replaces the retired record-debugging-evidence, record-maintenance-evidence, and record-outcome skills.

- Skill: `bhangeef16/record-evidence` (Agent Skill)
- Install (CLI): `npx skillmds@latest add bhangeef16/record-evidence`
- Raw SKILL.md: https://api.skillmd.com/api/skills/bhangeef16/record-evidence/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: BhangeeF16 (https://skillmd.com/u/bhangeef16)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/bhangeef16/record-evidence

---


# Record Evidence — $action

One procedure for making a run's results durable. Evidence or a decision that lives only in a session transcript did not happen, as far as the next reader can tell.

## Your contract

The dispatch prompt quotes this action's `required_inputs` and `required_outputs` verbatim from the action's own entry in the currently-injected `commands/<name>.process.yaml`. A dispatch that arrives without them is malformed — report `blocked` and name the missing contract rather than guessing at one.

## Procedure (every action)

1. Identify where the next reader will look for this record — the active plan, the audit record, the target's status record — and file it there, not in a new ad-hoc location.
2. Link to artifacts that already live elsewhere rather than restating them; a restated copy is a future drift defect.
3. State explicitly anything that was not done and why, alongside what was.

## Action-specific rules

- `record_debugging_evidence` — the full trail (reproduction, demonstrated root cause, minimal fix, passing regression validation) goes where the next investigator of this area will find it.
- `record_maintenance_evidence` — the maintenance pass's evidence (drift report, repairs, refresh output) filed into the active plan or audit record so the maintenance claim is checkable later.
- `record_outcome` — the run's terminal recording step: the target's status record updated to the final decision in the same change set as the evidence links that back it, per the delivery-governance state contract.

## Result

Report each required output produced (with its location), the result (pass / pass_with_risks / blocked / failure), and blocking questions as an explicit list (empty list stated explicitly).