954 B
954 B
name, description
| name | description |
|---|---|
| task-breakdown | Break down complex tasks into test lists Use when: planning work, decomposing features, tracking task progress, or organizing multi-step implementations. Attach file locations and implementation details as multi line comment after test description. |
Task Breakdown & Progress Tracking
This skill provides the workflow for decomposing complex tasks into tracked subtasks and managing their lifecycle using simple test lists
Core Principle
Always write a list of test names as individual comments in the test file
The executing agent will use this list to implement
Workflow
1. Break Down a Task
Ask the user clarifying questions. One question at a time. Make a test list with the user. Each test should fail.
Ask the user clarifications about the domain concepts and api. Write the decision in the test file as well
Add the minimal amount of functionality, only what the test requires.