The next person losing the same afternoon to the same trap, or a new rule for something that happened once and cost nothing.
Add "Find what slowed this work down" from ntent to this repo.
Fetch https://ntent.app/r/f/prompt-close-out as plain text. Use it as written, replacing anything in [brackets].
Then check it: Every finding names where it happened and what it cost, and says which rung its fix sits on.Reads https://ntent.app/r/f/prompt-close-out
Read the prompt
11 lines
This work is finished. List what made it slower or riskier than it needed to be. Go through it in four parts: finding out how things work, building, checking, and shipping.
Keep a finding only if you can point to where it happened (a file, a commit, an error, a correction someone made) and say what it cost (time, a bug, a redo). Drop the rest. Merge findings that share one cause.
For each finding, pick the strongest fix that works, and say why each stronger one does not:
1. Make the mistake impossible: a type, a schema, or the contract.
2. Catch it before merge: a lint rule, a check, or a test.
3. Make the right way easy to find: a script, a command, a doctor line.
4. A sentence in AGENTS.md that cites the incident. Last resort. Prefer tightening a rule that already exists over adding a new one.
Write each finding as: what happened, where, what it cost, the rung and the exact change, and how to check the change works. Check [WHERE FOLLOW-UP WORK LIVES] for one already open. Do not make any of these changes now.How to tell it works: Every finding names where it happened and what it cost, and says which rung its fix sits on.