conductor-implement
Execute tasks from a track's implementation plan following TDD workflow
By sickn33 · 384 installs
npx skills add sickn33/agentic-awesome-skills --skill conductor-implement
Source repository · Upstream listing
Implement Track
Execute tasks from a track's implementation plan, following the workflow rules defined in conductor/workflow.md .
Use this skill when
Working on implement track tasks or workflows
Needing guidance, best practices, or checklists for implement track
Do not use this skill when
The task is unrelated to implement track
You need a different domain or tool outside this scope
Instructions
Clarify goals, constraints, and required inputs.
Apply relevant best practices and validate outcomes.
Provide actionable steps and verification.
If detailed examples are required, open resources/implementation playbook.md .
Pre flight Checks
1. Verify Conductor is initialized:
Check conductor/product.md exists
Check conductor/workflow.md exists
Check conductor/tracks.md exists
If missing: Display error and suggest running /conductor:setup first
2. Load workflow configuration:
Read conductor/workflow.md
Parse TDD strictness level
Parse commit strategy
Parse verification checkpoint rules
Track Selection
If argument provided:
Validate track exists: conductor/tracks/{argument}/plan.md
If not found: Search for partial matches, suggest corrections
If no argument:
1. Read conductor/tracks.md
2. Parse for incomplete tracks (status [ ] or [~] )
3. Display selection menu:
Context Loading
Load all relevant context for implementation:
1. Track documents:
conductor/tracks/{trackId}/spec.md Requirements
conductor/tracks/{trackId}/plan.md Task list
conductor/tracks/{trackId}/metadata.json Progress state
2. Project context:
conductor/product.md Product understanding
conductor/tech stack.md Technical constraints
conductor/workflow.md Process rules
3. Code style (if exists):
conductor/code styleguides/{language}.md
Track Status Update
Update track to in progress:
1. In conductor/tracks.md :
Change [ ] to [~] for this track
2. In conductor/tracks/{trackId}/metadata.json :
Set status: "in progress"
Update updated timestamp
Task Execution Loop
For each incomplete task in plan.md (marked with [ ] ):
1. Task Identification
Parse plan.md to find next incomplete task:
Look for lines matching [ ] Task X.Y: {description}
Track current phase from structure
2. Task Start
Mark task as in progress:
Update plan.md: Change [ ] to [~] for current task
Announce: "Starting Task X.Y: {description}"
3. TDD Workflow (if TDD enabled in workflow.md)
Red Phase Write Failing Test:
Create test file if needed
Write test(s) for the task functionality
Run tests to confirm they fail
If tests pass unexpectedly: HALT, investigate
Green Phase Implement:
Write minimum code to make test pass
Run tests to confirm they pass
If tests fail: Debug and fix
Refactor Phase:
Clean up code
Run tests to ensure still passing
4. Non TDD Workflow (if TDD not strict)
Implement the task directly
Run any existing tests
Manual verification as needed
5. Task Completion
Commit changes (following commit strategy from workflow.md):
Update plan.md:
Change [~] to [x] for completed task
Commit plan update:
Update metadata.json:
Increment tasks.completed
Update updated timestamp
6. Phase Completion Check
After each task, check if phase is complete:
Parse plan.md for phase structure
If all tasks in current phase are [x] :
Run phase verification:
Execute verification tasks listed for the phase
Run full test suite: npm test / pytest / etc.
Report and wait for approval:
CRITICAL: Wait for explicit user approval before proceeding to next phase.
Error Handling During Implementation
On Tool Failure
HALT and present options
Do NOT automatically continue
On Test Failure
On Git Failure
Track Completion
When all phases and tasks are complete:
1. Final Verification
Run full test suite
Check all acceptance criteria from spec.md
Generate verification report
2. Update Track Status
In conductor/tracks.md :
Change [~] to [x] for this track
Update the "Updated" column
In conductor/tracks/{trackId}/metadata.json :
Set status: "complete"
Set phases.completed to total
Set tasks.completed to total
Update updated timestamp
In conductor/tracks/{trackId}/plan.md :
Update header status to [x] Complete
3. Documentation Sync Offer
4. Cleanup Offer
5. Completion Summary
Progress Tracking
Maintain progress in metadata.json throughout:
Resumption
If implementation is paused and resumed:
1. Load metadata.json for current state
2. Find current task from current task field
3. Check if task is [~] in plan.md
4. Ask user:
Critical Rules
1. NEVER skip verification checkpoints Always wait for user approval between phases
2. STOP on any failure Do not attempt to continue past errors
3. Follow workflow.md strictly TDD, commit strategy, and verification rules are mandatory
4. Keep plan.md updated Task status must reflect actual progress
5. Commit frequently Each task completion should be committed
6. Track all commits Record commit hashes in metadata.json for potential revert
Limitations
Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.