For agents

All tasks

Task

Close out a piece of work

Show the work does what you say, then turn what slowed it down into fewer surprises next time.

4 stepsproductdesignengineering
Paste into your coding agent
Show the work does what you say, then turn what slowed it down into fewer surprises next time.

Fetch https://ntent.app/r/task/close-out.json and follow it. Stop and ask me at any step that says to, and do not decide something on my behalf that the plan says is mine to decide.

Reads https://ntent.app/r/task/close-out.json

The steps

Here so you can follow along, or do it yourself. Your agent gets the same list from the plan above.

STRONGEST FIRST 01SHOW IT WORKS 02LIST SLOWDOWNS 03PICK THE RUNG 04ONE FIX PER TICKET CLAIM TABLE TYPE CHECK SCRIPT SENTENCE OWN TICKET
  1. 01

    Show it works

    Before you say done, list each claim with the command you ran, what it returned, and where the evidence is. A claim you did not check stays in the table and says so. From tier 2, add this section to AGENTS.md if it is not there yet. On a spike, leave AGENTS.md alone and put the table in your message.

    uses Proof of done

    How to tell it works: Someone who was not there can re-run any row and get the result it gives.

  2. 02

    List what slowed you down

    Go through finding out, building, checking and shipping in turn. Keep a finding only when you can point to where it happened and say what it cost. Merge findings that share one cause.

    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 a file, commit, error or correction, and a cost in time or bugs. None of them is "the docs could be clearer".

  3. 03

    Put each fix on the strongest rung

    Make the mistake impossible with a type, schema or the contract. If that cannot work, catch it before merge with a lint rule, check or test. If that cannot work, make the right way easy to find with a script or a doctor line. A sentence in AGENTS.md comes last, and it cites the incident. Prefer tightening a rule that exists to adding one.

    How to tell it works: Each finding names its rung and says why the rung above it does not fit.

  4. 04

    Land each fix on its own

    Do not edit AGENTS.md or add a check inside the change you are closing. Check the finding is not already open, then file it as its own piece of work, written so someone can start it without this conversation. Whether to take it on is the owner’s call, not the agent’s.

    How to tell it works: The change you are closing has no rule edits in it, and every finding is a ticket someone could pick up cold.

All tasks