Generate and Plan New Code Tracks

This skill creates a new Conductor "track" - a feature, bug fix, chore, or refactor - with a detailed specification and a phased implementation plan. It first verifies Conductor is initialized (conductor/product.md, tech-stack.md, and workflow.md exist, suggesting /conductor:setup if not) and loads those files for product, technical, and TDD/commit context. It classifies the track type, then interviews the user one question at a time, tailored by type and capped at six questions - for a feature: summary, user story, acceptance criteria, dependencies, scope boundaries, and optional technical notes; for a bug: summary, reproduction steps, expected versus actual behavior, affected areas, and an optional root-cause hypothesis; for a chore or refactor: task summary, motivation, success criteria, and risk assessment. It generates a track ID as {shortname}_{YYYYMMDD}, checking conductor/tracks.md for collisions and appending a counter if needed, then writes spec.md from the answers and presents it for approval (accept, edit inline, or start over) before generating a phased plan.md.

Use it to start a new unit of work in a Conductor-managed project that needs a written spec and a phased plan before implementation begins. It does not apply outside new-track creation - a different domain or tool is out of scope, and it will not proceed without Conductor already initialized.

Inputs: an optional initial description of the work, and the user's answers to the interview questions for the track's type. Outputs: conductor/tracks/{trackId}/spec.md (summary, context, user story or problem description, acceptance criteria, dependencies, out-of-scope items, technical notes), plan.md (an overview plus phases - typically Setup/Foundation, Core Implementation, Integration, and Polish - each with tasks and a verification step; TDD tracks get test-writing tasks before implementation tasks), metadata.json (id, title, type, status, phase and task counts), and index.md (a navigation page with progress). The track is also registered as a row in conductor/tracks.md and added to the "Active Tracks" section of conductor/index.md.

The Conductor track-management system: its product.md/tech-stack.md/workflow.md context files, its tracks.md registry, and its /conductor:implement and /conductor:status commands referenced as the next steps after a track is created. On any directory or file-write failure, it halts, does not register the track in tracks.md, and cleans up the partial track rather than leaving an inconsistent state.

{
  "id": "{trackId}",
  "title": "{Track Title}",
  "type": "feature|bug|chore|refactor",
  "status": "pending"
}

Developers using Conductor who want a new feature, bug fix, chore, or refactor turned into a reviewed spec and a phased, verifiable implementation plan before they start coding.