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

- 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:

```

Select a track to implement:

In Progress:

1. [~] auth_20250115 - User Authentication (Phase 2, Task 3)

Pending:

2. [ ] nav-fix_20250114 - Navigation Bug Fix

3. [ ] dashboard_20250113 - Dashboard Feature

Enter number or track ID:

```

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:**

Following TDD workflow for Task X.Y...

Step 1: Writing 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:**

Step 2: Implementing minimal code to pass test

- Write minimum code to make test pass

- Run tests to confirm they pass

- If tests fail: Debug and fix

**Refactor Phase:**

Step 3: Refactoring while keeping tests green

- 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):

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

**Update plan.md:**

- Change `[~]` to `[x]` for completed task

- Commit plan update:

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

**Update metadata.json:**