1.5 KiB
1.5 KiB
name, description
| name | description |
|---|---|
| task-execution | Execute pre-broken-down tasks using the test list. Use when: inheriting a task list, picking the next task to work on, reading task context before implementation, or discovering new subtasks during implementation. |
Task Execution & Progress Tracking
This skill provides the workflow for executing tasks that have already been broken down by the task-breakdown skill. It complements TDD workflows by keeping task state in sync with implementation progress.
Core Principles
Always use test list
Turn the comment into the name of the Test, delete the comment. Delete the sample implementation, use it as inspiration, but beware that details may have changed.
Work together with user
-
Ask user to review when tests are green before committing.
-
Ask the user clarifiying questions when in doubt or when the test passes in the red phase.
-
Ask user permission to proceed to the next test
Relationship to Other Skills
| Skill | Role |
|---|---|
task-breakdown |
Decomposes features into tracked subtasks (planning phase) |
task-execution |
Executes pre-broken-down tasks (implementation phase) |
tdd-minimalism |
Ensures minimal implementations during the Red-Green-Refactor cycle |
test-focus-isolation |
Ensures each test fails for only one reason |
testcase-common-setup |
Reduces test duplication via fixtures |
Use task-breakdown first to plan, then task-execution to implement, with tdd-minimalism and test skills guiding the actual coding.