Get tests green, docs clear
Run tests and polish the README until npm test passes and documentation is complete.
Use this when
A repo where npm test currently fails and the README has drifted from reality — typically an inherited project or one returning from a long pause. Use it when both halves are genuinely checkable; if "clear docs" means a rewrite you have opinions about, do that yourself.
Done when
✓ npm test exiting zero is the hard gate. The documentation half has no machine check, so review the README diff yourself before committing — an agent will happily describe intent it inferred rather than behaviour it confirmed.
Why it works
This is a /goal, not an open loop: the end state is verifiable (the suite exits zero) so the agent has a real stopping line instead of an interval. Pairing the docs pass with the test pass works because the agent has just read the code it is documenting, which is when the README is cheapest to fix.
Source: TrebuchetDynamics ↗graded C · 70/100 — how grades work →
More testing loops
Build a REST API with tests
Run autonomous iterations to ship a complete REST API with full test coverage until completion is promised.
Test all endpoints
Run tests against every API endpoint until coverage is complete or you hit 30 iterations.
Hit acceptance criteria
Drive a feature to done against explicit acceptance criteria: a working paginated endpoint, passing tests, clean lint, and a hard turn cap.