conductor-implement

Implement Track

Execute tasks from a track's implementation plan, following the workflow rules defined in conductor/workflow.md.

Use this skill when

Do not use this skill when

Instructions

Pre-flight Checks

Track Selection

If argument provided:

If no argument:

```

Select a track to implement:

In Progress:

Pending:

Enter number or track ID:

```

Context Loading

Load all relevant context for implementation:

Track Status Update

Update track to in-progress:

Task Execution Loop

For each incomplete task in plan.md (marked with [ ]):

1. Task Identification

Parse plan.md to find next incomplete task:

2. Task Start

Mark task as in-progress:

3. TDD Workflow (if TDD enabled in workflow.md)

Red Phase - Write Failing Test:

Following TDD workflow for Task X.Y...

Step 1: Writing failing test

Green Phase - Implement:

Step 2: Implementing minimal code to pass test

Refactor Phase:

Step 3: Refactoring while keeping tests green

4. Non-TDD Workflow (if TDD not strict)

5. Task Completion

Commit changes (following commit strategy from workflow.md):

git add -A
git commit -m "{commit_prefix}: {task description} ({trackId})"

Update plan.md:

git add conductor/tracks/{trackId}/plan.md
git commit -m "chore: mark task X.Y complete ({trackId})"

Update metadata.json:

6. Phase Completion Check

After each task, check if phase is complete:

Run phase verification:

Phase {N} complete. Running verification...

Report and wait for approval:

Phase {N} Verification Results:
- All phase tasks: Complete
- Tests: {passing/failing}
- Verification: {pass/fail}

Approve to continue to Phase {N+1}?
1. Yes, continue
2. No, there are issues to fix
3. Pause implementation

CRITICAL: Wait for explicit user approval before proceeding to next phase.

Error Handling During Implementation

On Tool Failure

ERROR: {tool} failed with: {error message}

Options:
1. Retry the operation
2. Skip this task and continue
3. Pause implementation
4. Revert current task changes

On Test Failure

TESTS FAILING after Task X.Y

Failed tests:
- {test name}: {failure reason}

Options:
1. Attempt to fix
2. Rollback task changes
3. Pause for manual intervention

On Git Failure

GIT ERROR: {error message}

This may indicate:
- Uncommitted changes from outside Conductor
- Merge conflicts
- Permission issues

Options:
1. Show git status
2. Attempt to resolve
3. Pause for manual intervention

Track Completion

When all phases and tasks are complete:

1. Final Verification

All tasks complete. Running final verification...

2. Update Track Status

In conductor/tracks.md:

In conductor/tracks/{trackId}/metadata.json:

In conductor/tracks/{trackId}/plan.md:

3. Documentation Sync Offer

Track complete! Would you like to sync documentation?

This will update:
- conductor/product.md (if new features added)
- conductor/tech-stack.md (if new dependencies added)
- README.md (if applicable)

1. Yes, sync documentation
2. No, skip

4. Cleanup Offer

Track {trackId} is complete.

Cleanup options:
1. Archive - Move to conductor/tracks/_archive/
2. Delete - Remove track directory
3. Keep - Leave as-is

5. Completion Summary

Track Complete: {track title}

Summary:
- Track ID: {trackId}
- Phases completed: {N}/{N}
- Tasks completed: {M}/{M}
- Commits created: {count}
- Tests: All passing

Next steps:
- Run /conductor:status to see project progress
- Run /conductor:new-track for next feature

Progress Tracking

Maintain progress in metadata.json throughout:

{
  "id": "auth_20250115",
  "title": "User Authentication",
  "type": "feature",
  "status": "in_progress",
  "created": "2025-01-15T10:00:00Z",
  "updated": "2025-01-15T14:30:00Z",
  "current_phase": 2,
  "current_task": "2.3",
  "phases": {
    "total": 3,
    "completed": 1
  },
  "tasks": {
    "total": 12,
    "completed": 7
  },
  "commits": [
    "abc1234: feat: add login form (auth_20250115)",
    "def5678: feat: add password validation (auth_20250115)"
  ]
}

Resumption

If implementation is paused and resumed:

```

Resuming track: {title}

Last task in progress: Task {X.Y}: {description}

Options:

```

Critical Rules