Progressively activates todo tests one at a time, updates implementation code until each passes (verified via Wallaby), checks off matching design doc progress, then moves to the next—following the design doc as the single source of truth.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Using the design doc at ${designDocPath} as the single source of truth, progressively activate the tests in ${testFilePath}.
${testFilePath} as:it.todo(...) into it(...), but do it strictly one test at a time, then update the implementation just enough for that specific test to turn green — NOTHING MORE.DO NOT IMPLEMENT ANYTHING THAT IS NOT DIRECTLY RELATED TO THE CURRENT TEST.
After the current test passes, update progress in ${designDocPath} (see Design Doc Progress below).
STOP when these tests are green.
Remove the wiprecation (@deprecated 🚧 work in progress) jsdoc from the implementated item if it is done and safe to use.
After each test turns green, update ${designDocPath} to reflect completed work.
Flip 🚧 to ✅ and - [ ] to - [x]. Do not edit any other text, headings, diagrams, or structure in the design doc.
Check off items in these sections only:
### 🚧 {test_title} heading that matches the test you just activated.- [ ] ...taslk description... item whose work is now done and verified by the passing test.## 🚧 {pr_title} entry when all PR's Tasks and Testing Strategy items are checked off.If you are unsure whether an Implementation Details item is done, leave it unchecked.
DO NOT IMPLEMENT EMPTY TESTS.
NEVER implement tests.
ONLY EDIT TESTS as a last resort after you have tried everything else.
Design doc edits are only checkbox-based or 🚧 to ✅ replacements. Never reword, reorder, add, or remove content in ${designDocPath}.
Run tests after each change. Only once the current test passes should you advance to the next one.
Use the Wallaby Skill if available to run tests, otherwise run tests using the recommended approach for the project.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Continues Charted Coding work for a PR by routing to scaffold, red, or green based on design doc progress. Use when resuming work on a PR, continuing TDD after a break, or when the user invokes charted continue with a design doc and PR number.
The English summary is being prepared. Showing the original description.
Interviews the user section by section to collaboratively produce design documents. Use when creating a design doc, starting feature design, or when the user invokes the design command.
The English summary is being prepared. Showing the original description.
Runs Charted Coding iterations in a loop — route via charted-continue, batch red or green work for an entire test file, commit, then repeat until the PR is complete. Infers design doc and PR number when omitted. Use when the user invokes charted loop, wants batch TDD for a PR test file, or asks to continue charted work with commits.
The English summary is being prepared. Showing the original description.
Writes the next failing test based on provided design doc and existing todo tests
The English summary is being prepared. Showing the original description.
Reviews a design doc with expert sub-agents
The English summary is being prepared. Showing the original description.
Writes work-in-progress code and tests based on design doc
The English summary is being prepared. Showing the original description.