Documentation
Write a Nightshift punch list
Define complete, verifiable engineering outcomes that survive long agent runs and handoffs.
Answers: write a coding-agent punch list · Updated
A strong punch-list item names one outcome, the exact change required, the evidence that proves it, and the intended commit. Keep items ordered and independently reviewable.
Item anatomy
Use one top-level checkbox per outcome. Sub-bullets define scope without creating hidden tasks. Verification should be runnable immediately before the commit.
- [ ] **2. Add recovery coverage.**
- Cover the missing-session fallback.
- Preserve the current successful-resume path.
- Verify: bats tests/watchman.bats
- Commit: `test: cover recovery fallback`Good definitions of done
Prefer observable outcomes over activity. “Improve tests” is open to interpretation; “cover the fallback and keep the watchman suite green” closes cleanly.
- Name the file, path, behavior, or user-visible outcome.
- State important invariants that must remain true.
- Use the narrowest trustworthy gate.
- Split outcomes that deserve separate review or rollback.
What does not belong
Do not put unresolved owner decisions in the item, and do not hide known future work in the parking lot. Draft first, promote only owner-approved work, and never delete an approved item to make the shift appear complete.
Start with a bounded prompt
This prompt names the outcome and preserves Nightshift’s review boundary. Paste it into the supported coding host from the project you want to change.
Help me turn this objective into ordered Nightshift items. Give every item one outcome, explicit scope, a Verify line, and a conventional commit subject.What this workflow does not claim
- Unresolved product decisions should be parked instead of hidden inside an active item.
- A broad activity such as 'improve tests' is not a complete definition of done.
Evidence and sources
These links support the released behavior, public outcomes, or problem language described on this page.