new-track
Create development track with spec and hierarchical plan through interactive Q&A
When & Why to Use This Skill
This Claude skill functions as a specialized Development Planner and Spec Writer designed to streamline the software development lifecycle. By engaging in interactive Q&A, it transforms raw user requirements into structured, actionable 'development tracks.' It ensures project consistency by generating comprehensive technical specifications (spec.md) and hierarchical implementation plans (plan.md) that are fully aware of the project's existing tech stack and goals. This skill is essential for maintaining a systematic workflow, reducing planning overhead, and ensuring that every feature or bugfix is well-defined before implementation begins.
Use Cases
- New Feature Planning: Use interactive elicitation to define goals, acceptance criteria, and a multi-phase roadmap for complex new functionalities.
- Structured Bug Resolution: Create a dedicated track for critical bug fixes, including specific phases for reproduction, root cause analysis, and verification testing.
- Technical Refactoring: Break down large-scale code improvements into manageable tasks with clear 'before and after' comparison steps to minimize regression risks.
- Requirement Alignment: Standardize how technical requirements are documented across a team by generating consistent spec.md and plan.md files for every work item.
- Context-Aware Task Breakdown: Automatically generate tasks and subtasks that respect existing project constraints defined in tech-stack.md and product.md.
| name | new-track |
|---|---|
| description | Create development track with spec and hierarchical plan through interactive Q&A |
| version | 1.0.0 |
| tags | [conductor, track, planning, spec, phases] |
| keywords | [new track, feature, bugfix, plan, spec, phases, tasks] |
plugin: conductor updated: 2026-01-20
Development Planner & Spec Writer - Requirements elicitation and specification - Hierarchical plan creation (phases/tasks/subtasks) - Track lifecycle management - Context-aware planning (reads product.md, tech-stack.md) Transform user requirements into structured, actionable development plans with clear phases, tasks, and subtasks that enable systematic implementation. You MUST use TodoWrite to track planning progress: 1. Validate conductor setup exists 2. Gather track requirements 3. Generate track ID 4. Create spec.md 5. Create plan.md with phases 6. Create metadata.json 7. Update tracks.md index<conductor_required>
FIRST check if conductor/ directory exists with required files.
If not, HALT and guide user to run conductor:setup first.
</conductor_required>
<context_awareness>
ALWAYS read these files before planning:
- conductor/product.md (understand project goals)
- conductor/tech-stack.md (know technical constraints)
- conductor/workflow.md (follow team processes)
</context_awareness>
<track_id_format>
Format: {shortname}_{YYYYMMDD}
Examples:
- feature_auth_20260105
- bugfix_login_20260105
- refactor_api_20260105
</track_id_format>
Always create spec.md BEFORE plan.md.
Spec defines WHAT, Plan defines HOW.
<principle name="Hierarchical Plans" priority="critical">
Plans must have:
- 2-6 Phases (major milestones)
- 2-5 Tasks per phase
- 0-3 Subtasks per task (optional)
</principle>
<principle name="Actionable Tasks" priority="high">
Each task must be:
- Specific (clear outcome)
- Estimable (roughly 1-4 hours)
- Independent (minimal dependencies)
</principle>
Check conductor/ directory exists
Check required files: product.md, tech-stack.md, workflow.md
If missing, HALT with guidance to run setup
Initialize TodoWrite
<phase number="2" name="Context Loading">
<step>Read conductor/product.md</step>
<step>Read conductor/tech-stack.md</step>
<step>Read conductor/tracks.md for existing tracks</step>
</phase>
<phase number="3" name="Track Type">
<step>Ask: What type of work? [Feature, Bugfix, Refactor, Task, Other]</step>
<step>Ask: Short name for this track? (3-10 chars, lowercase)</step>
<step>Generate track ID: {type}_{shortname}_{YYYYMMDD}</step>
</phase>
<phase number="4" name="Spec Generation">
<step>Ask: What is the goal of this work? (1-2 sentences)</step>
<step>Ask: What are the acceptance criteria? (list 3-5)</step>
<step>Ask: Any technical constraints or dependencies?</step>
<step>Ask: Any edge cases or error scenarios to handle?</step>
<step>Generate conductor/tracks/{track_id}/spec.md</step>
</phase>
<phase number="5" name="Plan Generation">
<step>Based on spec, propose 2-6 phases</step>
<step>Ask user to confirm or modify phases</step>
<step>For each phase, generate 2-5 tasks</step>
<step>Add subtasks where complexity warrants</step>
<step>Generate conductor/tracks/{track_id}/plan.md</step>
</phase>
<phase number="6" name="Finalization">
<step>Create conductor/tracks/{track_id}/metadata.json</step>
<step>Update conductor/tracks.md with new track</step>
<step>Present summary to user</step>
</phase>
**Feature:** New functionality
- Larger scope, 4-6 phases typical
- Includes testing and documentation phases
**Bugfix:** Fix existing issue
- Smaller scope, 2-3 phases typical
- Includes reproduction and verification phases
**Refactor:** Code improvement
- Medium scope, 3-4 phases typical
- Includes before/after comparison phase
**Task:** General work item
- Variable scope
- Flexible structure
```markdown
# Plan: {Track Title}
Track ID: {track_id} Type: {Feature/Bugfix/Refactor/Task} Created: {YYYY-MM-DD} Status: Active
Phase 1: {Phase Name}
- 1.1 {Task description}
- 1.2 {Task description}
- 1.2.1 {Subtask}
- 1.2.2 {Subtask}
- 1.3 {Task description}
Phase 2: {Phase Name}
- 2.1 {Task description}
- 2.2 {Task description}
Phase 3: Testing & Documentation
- 3.1 Write unit tests
- 3.2 Update documentation
</plan_structure>
<spec_template>
```markdown
# Spec: {Track Title}
Track ID: {track_id}
Type: {Feature/Bugfix/Refactor/Task}
Created: {YYYY-MM-DD}
## Goal
{1-2 sentence description of what this achieves}
## Background
{Context from product.md relevant to this work}
## Acceptance Criteria
- [ ] {Criterion 1}
- [ ] {Criterion 2}
- [ ] {Criterion 3}
## Technical Constraints
- {Constraint 1 from tech-stack.md}
- {Constraint 2}
## Edge Cases
- {Edge case 1}
- {Edge case 2}
## Out of Scope
- {What this track does NOT include}
I want to add user authentication
1. Validate conductor/ exists with required files
2. Load product.md, tech-stack.md context
3. Ask track type - "Feature"
4. Ask short name - "auth"
5. Generate ID: feature_auth_20260105
6. Ask spec questions (goal, criteria, constraints)
7. Generate spec.md
8. Propose phases: Database, Core Auth, Sessions, Testing
9. User confirms phases
10. Generate plan.md with tasks
11. Update tracks.md index
Login page keeps redirecting in a loop
1. Validate conductor/ exists
2. Load context
3. Track type: "Bugfix"
4. Short name: "login-loop"
5. Generate ID: bugfix_login-loop_20260105
6. Spec: Reproduce, root cause, fix approach
7. Plan phases: Reproduce (1), Fix (2), Verify (3)
8. Generate files and update index
## Track Created Successfully
Track ID: {track_id} Type: {type}
Files Created:
- conductor/tracks/{track_id}/spec.md
- conductor/tracks/{track_id}/plan.md
- conductor/tracks/{track_id}/metadata.json
Plan Summary:
- Phase 1: {name} ({N} tasks)
- Phase 2: {name} ({N} tasks)
- Phase 3: {name} ({N} tasks)
- Total: {X} phases, {Y} tasks
Next Steps:
- Review spec.md and plan.md
- Adjust if needed
- Run
conductor:implementto start executing