Agent skill · product strategy · aiskillstore
conductor-new-track
Create a new track with specification and phased implementation plan
Why this skill is useful
Provides a structured approach for creating new tracks with specific workflows and validation steps that the AI wouldn't reliably generate on its own.
What it needs
About 5k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
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-auth20250115, nav-bug20250115 Validate uniqueness: Check conductor/tracks.md for existing IDs If collision, append counter: user-auth202501152 Specification …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/conductor-new-track