conductor-implementlisted

# 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 (Ph