Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
SkillScore73Maintained
Automatic
◆Coding pack
Last verified 8/29/2026
What it changes
Passed 15 of 20 test cases with the skill, and 8 of 20 without it.
Without skill41%
With skill73%
Checks it passed that the model alone missed
Marks blocked task with `[!]` symbol.
Sets Checkpoints table status column to verified.
Uses `[~]` symbol to designate in-progress status.
and 8 more in the full report
7 fixed9 passed either way6 still failing0 broke
Pass-rate lift
+32 pp
Tokens
+157%
Agent turns
0%
Response time
-40%
Model gemini-3.6-flashMeasured 8/29/2026v116 of 22 cases passed with skill · 20 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 7
Prompt
After updating plan.md to show Task 1.2 is complete, what git commit command should be executed for the plan file change?
What was checked, without and with the skill
Checked
Without skill
With skill
Formats commit message starting with docs: update plan - task 1.2 complete.
Missed
Passed
Includes Track: metadata in commit message footer.
Missed
Passed
case-09 · gemini-3.6-flash · 8/29/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md617 linessingle file
Workflow Patterns
Guide for implementing tasks using Conductor's TDD workflow, managing phase checkpoints, handling git commits, and executing the verification protocol that ensures quality throughout implementation.
When to Use This Skill
Implementing tasks from a track's plan.md
Following TDD red-green-refactor cycle
Completing phase checkpoints
Managing git commits and notes
Understanding quality assurance gates
Handling verification protocols
Recording progress in plan files
TDD Task Lifecycle
Follow these 11 steps for each task:
Step 1: Select Next Task
Read plan.md and identify the next pending [ ] task. Select tasks in order within the current phase. Do not skip ahead to later phases.
Step 2: Mark as In Progress
Update plan.md to mark the task as [~]:
- [~] **Task 2.1**: Implement user validation
Commit this status change separately from implementation.
Step 3: RED - Write Failing Tests
Write tests that define the expected behavior before writing implementation: