dev-receipts
Installation
SKILL.md
Dev receipts
Every claim about a change carries a receipt: a test, a command and its output, a screenshot, a step someone can repeat. Done means every acceptance row has one. This runs a change from request to PR in five steps. A step the user has already covered, such as an approved spec, is skipped.
1. Spec: write down what done means
Before the first line of code, write the spec to disk, where the repo keeps specs or else docs/specs/YYYY-MM-DD-<slug>.md. A plan kept in your head is gone after compaction, and the user cannot correct what they never saw.
# <change>
Ask: "<the user's words>"
Smallest version: <the one that meets the ask and its deadline>
Assumptions: <each guess that changes what gets built, one per line>
Not doing: <what someone might expect that you are leaving out>
## Acceptance
| # | When | Then | Receipt |
| 1 | <action or input> | <observable result> | <test name, command, screenshot or walk step> |