New Track Create a new track (feature, bug fix, chore, or refactor) with a detailed specification and phased implementation plan. Use this skill when Working on new track tasks or workflows Needing guidance, best practices, or checklists for new track Do not use this skill when The task is unrelated to new 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/tech stack.md exists Check conductor/workflow.md exists If missing: Display error and suggest running /conductor:setup first 2. Load context files: Read conductor/product.md for product context Read conductor/tech stack.md for technical context Read conductor/workflow.md for TDD/commit preferences Track Classification Determine track type based on description or ask user: Interactive Specification Gathering CRITICAL RULES: Ask ONE question per turn Wait for user response before proceeding Tailor questions based on track type Maximum 6 questions total For Feature Tracks Q1: Feature Summary Q2: User Story Q3: Acceptance Criteria Q4: Dependencies Q5: Scope Boundaries Q6: Technical Considerations (optional) For Bug Tracks Q1: Bug Summary Q2: Steps to Reproduce Q3: Expected vs Actual Behavior Q4: Affected Areas Q5: Root Cause Hypothesis (optional) For Chore/Refactor Tracks Q1: Task Summary Q2: Motivation Q3: Success Criteria Q4: Risk Assessment Track ID Generation Generate track ID in format: {shortname} {YYYYMMDD} Extract shortname from feature/bug summary (2 3 words, lowercase, hyphenated) Use current date Example: user auth 20250115 , nav bug 20250115 Validate uniqueness: Check conductor/tracks.md for existing IDs If collision, append counter: user auth 20250115 2 Specification Generation Create conductor/tracks/{trackId}/spec.md : User Review of Spec Display the generated spec and ask: Plan Generation After spec approval, generate conductor/tracks/{trackId}/plan.md : Plan Structure Phase Guidelines Group related tasks into logical phases Each phase should be independently verifiable Include verification task after each phase TDD tracks: Include test writing tasks before implementation tasks Typical structure: 1. Setup/Foundation Initial scaffolding, interfaces 2. Core Implementation Main functionality 3. Integration Connect with existing system 4. Polish Error handling, edge cases, docs User Review of Plan Display the generated plan and ask: Track Creation After plan approval: 1. Create directory structure: 2. Create metadata.json : 3. Create index.md : 4. Register in conductor/tracks.md : Add row to tracks table Format: [ ] {trackId} {title} {created} {created} 5. Update conductor/index.md : Add track to "Active Tracks" section Completion Message Error Handling If directory creation fails: Halt and report, do not register in tracks.md If any file write fails: Clean up partial track, report error If tracks.md update fails: Warn user to manually register track

conductor-new-track