charted-green
Context
- designDocPath: $ARGUMENTS[0]
- testFilePath: $ARGUMENTS[1]
Goal
Using the design doc at ${designDocPath} as the single source of truth, progressively activate the tests in ${testFilePath}.
Steps
Categorize each test in ${testFilePath} as:
- Implemented tests: tests that contain actual test code (not just empty or comments)
- Empty tests: tests that are empty or only contain comments - TOTALLY IGNORE THESE
For each implemented test, convert 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.
More from marmicode/skills
charted-review
Reviews a design doc with expert sub-agents
25charted-design
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.
22charted-red
Writes the next failing test based on provided design doc and existing todo tests
21charted-scaffold
Writes work-in-progress code and tests based on design doc
20charted-wip
Writes wip code and tests based on design doc
1