Conductor Implement

1---
2name: conductor-implement
3description: Execute tasks from a track's implementation plan following TDD workflow
4metadata:
5  argument-hint: "[track-id] [--task X.Y] [--phase N]"
6---
7 
8# Implement Track
9 
10Execute tasks from a track's implementation plan, following the workflow rules defined in `conductor/workflow.md`.
11 
12## Use this skill when
13 
14- Working on implement track tasks or workflows
15- Needing guidance, best practices, or checklists for implement track
16 
17## Do not use this skill when
18 
19- The task is unrelated to implement track
20- You need a different domain or tool outside this scope
21 
22## Instructions
23 
24- Clarify goals, constraints, and required inputs.
25- Apply relevant best practices and validate outcomes.
26- Provide actionable steps and verification.
27- If detailed examples are required, open `resources/implementation-playbook.md`.
28 
29## Pre-flight Checks
30 
311. Verify Conductor is initialized:
32   - Check `conductor/product.md` exists
33   - Check `conductor/workflow.md` exists
34   - Check `conductor/tracks.md` exists
35   - If missing: Display error and suggest running `/conductor:setup` first
36 
372. Load workflow configuration:
38   - Read `conductor/workflow.md`
39   - Parse TDD strictness level
40   - Parse commit strategy
41   - Parse verification checkpoint rules
42 
43## Track Selection
44 
45### If argument provided:
46 
47- Validate track exists: `conductor/tracks/{argument}/plan.md`
48- If not found: Search for partial matches, suggest corrections
49 
50### If no argument:
51 
521. Read `conductor/tracks.md`
532. Parse for incomplete tracks (status `[ ]` or `[~]`)
543. Display selection menu:
55 
56   ```
57   Select a track to implement:
58 
59   In Progress:
60   1. [~] auth_20250115 - User Authentication (Phase 2, Task 3)
61 
62   Pending:
63   2. [ ] nav-fix_20250114 - Navigation Bug Fix
64   3. [ ] dashboard_20250113 - Dashboard Feature
65 
66   Enter number or track ID:
67   ```
68 
69## Context Loading
70 
71Load all relevant context for implementation:
72 
731. Track documents:
74   - `conductor/tracks/{trackId}/spec.md` - Requirements
75   - `conductor/tracks/{trackId}/plan.md` - Task list
76   - `conductor/tracks/{trackId}/metadata.json` - Progress state
77 
782. Project context:
79   - `conductor/product.md` - Product understanding
80   - `conductor/tech-stack.md` - Technical constraints
81   - `conductor/workflow.md` - Process rules
82 
833. Code style (if exists):
84   - `conductor/code_styleguides/{language}.md`
85 
86## Track Status Update
87 
88Update track to in-progress:
89 
901. In `conductor/tracks.md`:
91   - Change `[ ]` to `[~]` for this track
92 
932. In `conductor/tracks/{trackId}/metadata.json`:
94   - Set `status: "in_progress"`
95   - Update `updated` timestamp
96 
97## Task Execution Loop
98 
99For each incomplete task in plan.md (marked with `[ ]`):
100 
101### 1. Task Identification
102 
103Parse plan.md to find next incomplete task:
104 
105- Look for lines matching `- [ ] Task X.Y: {description}`
106- Track current phase from structure
107 
108### 2. Task Start
109 
110Mark task as in-progress:
111 
112- Update plan.md: Change `[ ]` to `[~]` for current task
113- Announce: "Starting Task X.Y: {description}"
114 
115### 3. TDD Workflow (if TDD enabled in workflow.md)
116 
117**Red Phase - Write Failing Test:**
118 
119```
120Following TDD workflow for Task X.Y...
121 
122Step 1: Writing failing test
123```
124 
125- Create test file if needed
126- Write test(s) for the task functionality
127- Run tests to confirm they fail
128- If tests pass unexpectedly: HALT, investigate
129 
130**Green Phase - Implement:**
131 
132```
133Step 2: Implementing minimal code to pass test
134```
135 
136- Write minimum code to make test pass
137- Run tests to confirm they pass
138- If tests fail: Debug and fix
139 
140**Refactor Phase:**
141 
142```
143Step 3: Refactoring while keeping tests green
144```
145 
146- Clean up code
147- Run tests to ensure still passing
148 
149### 4. Non-TDD Workflow (if TDD not strict)
150 
151- Implement the task directly
152- Run any existing tests
153- Manual verification as needed
154 
155### 5. Task Completion
156 
157**Commit changes** (following commit strategy from workflow.md):
158 
159```bash
160git add -A
161git commit -m "{commit_prefix}: {task description} ({trackId})"
162```
163 
164**Update plan.md:**
165 
166- Change `[~]` to `[x]` for completed task
167- Commit plan update:
168 
169```bash
170git add conductor/tracks/{trackId}/plan.md
171git commit -m "chore: mark task X.Y complete ({trackId})"
172```
173 
174**Update metadata.json:**
175 
176- Increment `tasks.completed`
177- Update `updated` timestamp
178 
179### 6. Phase Completion Check
180 
181After each task, check if phase is complete:
182 
183- Parse plan.md for phase structure
184- If all tasks in current phase are `[x]`:
185 
186**Run phase verification:**
187 
188```
189Phase {N} complete. Running verification...
190```
191 
192- Execute verification tasks listed for the phase
193- Run full test suite: `npm test` / `pytest` / etc.
194 
195**Report and wait for approval:**
196 
197```
198Phase {N} Verification Results:
199- All phase tasks: Complete
200- Tests: {passing/failing}
201- Verification: {pass/fail}
202 
203Approve to continue to Phase {N+1}?
2041. Yes, continue
2052. No, there are issues to fix
2063. Pause implementation
207```
208 
209**CRITICAL: Wait for explicit user approval before proceeding to next phase.**
210 
211## Error Handling During Implementation
212 
213### On Tool Failure
214 
215```
216ERROR: {tool} failed with: {error message}
217 
218Options:
2191. Retry the operation
2202. Skip this task and continue
2213. Pause implementation
2224. Revert current task changes
223```
224 
225- HALT and present options
226- Do NOT automatically continue
227 
228### On Test Failure
229 
230```
231TESTS FAILING after Task X.Y
232 
233Failed tests:
234- {test name}: {failure reason}
235 
236Options:
2371. Attempt to fix
2382. Rollback task changes
2393. Pause for manual intervention
240```
241 
242### On Git Failure
243 
244```
245GIT ERROR: {error message}
246 
247This may indicate:
248- Uncommitted changes from outside Conductor
249- Merge conflicts
250- Permission issues
251 
252Options:
2531. Show git status
2542. Attempt to resolve
2553. Pause for manual intervention
256```
257 
258## Track Completion
259 
260When all phases and tasks are complete:
261 
262### 1. Final Verification
263 
264```
265All tasks complete. Running final verification...
266```
267 
268- Run full test suite
269- Check all acceptance criteria from spec.md
270- Generate verification report
271 
272### 2. Update Track Status
273 
274In `conductor/tracks.md`:
275 
276- Change `[~]` to `[x]` for this track
277- Update the "Updated" column
278 
279In `conductor/tracks/{trackId}/metadata.json`:
280 
281- Set `status: "complete"`
282- Set `phases.completed` to total
283- Set `tasks.completed` to total
284- Update `updated` timestamp
285 
286In `conductor/tracks/{trackId}/plan.md`:
287 
288- Update header status to `[x] Complete`
289 
290### 3. Documentation Sync Offer
291 
292```
293Track complete! Would you like to sync documentation?
294 
295This will update:
296- conductor/product.md (if new features added)
297- conductor/tech-stack.md (if new dependencies added)
298- README.md (if applicable)
299 
3001. Yes, sync documentation
3012. No, skip
302```
303 
304### 4. Cleanup Offer
305 
306```
307Track {trackId} is complete.
308 
309Cleanup options:
3101. Archive - Move to conductor/tracks/_archive/
3112. Delete - Remove track directory
3123. Keep - Leave as-is
313```
314 
315### 5. Completion Summary
316 
317```
318Track Complete: {track title}
319 
320Summary:
321- Track ID: {trackId}
322- Phases completed: {N}/{N}
323- Tasks completed: {M}/{M}
324- Commits created: {count}
325- Tests: All passing
326 
327Next steps:
328- Run /conductor:status to see project progress
329- Run /conductor:new-track for next feature
330```
331 
332## Progress Tracking
333 
334Maintain progress in `metadata.json` throughout:
335 
336```json
337{
338  "id": "auth_20250115",
339  "title": "User Authentication",
340  "type": "feature",
341  "status": "in_progress",
342  "created": "2025-01-15T10:00:00Z",
343  "updated": "2025-01-15T14:30:00Z",
344  "current_phase": 2,
345  "current_task": "2.3",
346  "phases": {
347    "total": 3,
348    "completed": 1
349  },
350  "tasks": {
351    "total": 12,
352    "completed": 7
353  },
354  "commits": [
355    "abc1234: feat: add login form (auth_20250115)",
356    "def5678: feat: add password validation (auth_20250115)"
357  ]
358}
359```
360 
361## Resumption
362 
363If implementation is paused and resumed:
364 
3651. Load `metadata.json` for current state
3662. Find current task from `current_task` field
3673. Check if task is `[~]` in plan.md
3684. Ask user:
369 
370   ```
371   Resuming track: {title}
372 
373   Last task in progress: Task {X.Y}: {description}
374 
375   Options:
376   1. Continue from where we left off
377   2. Restart current task
378   3. Show progress summary first
379   ```
380 
381## Critical Rules
382 
3831. **NEVER skip verification checkpoints** - Always wait for user approval between phases
3842. **STOP on any failure** - Do not attempt to continue past errors
3853. **Follow workflow.md strictly** - TDD, commit strategy, and verification rules are mandatory
3864. **Keep plan.md updated** - Task status must reflect actual progress
3875. **Commit frequently** - Each task completion should be committed
3886. **Track all commits** - Record commit hashes in metadata.json for potential revert
389