Conductor New Track

1---
2name: conductor-new-track
3description: Create a new track with specification and phased implementation plan
4metadata:
5  argument-hint: <feature|bug|chore|refactor> <name>
6---
7 
8# New Track
9 
10Create a new track (feature, bug fix, chore, or refactor) with a detailed specification and phased implementation plan.
11 
12## Use this skill when
13 
14- Working on new track tasks or workflows
15- Needing guidance, best practices, or checklists for new track
16 
17## Do not use this skill when
18 
19- The task is unrelated to new track
20- You need a different domain or tool outside this scope
21 
22## Instructions
23 
24- Clarify goals, constraints, and required inputs.
25- Apply relevant best practices and validate outcomes.
26- Provide actionable steps and verification.
27- If detailed examples are required, open `resources/implementation-playbook.md`.
28 
29## Pre-flight Checks
30 
311. Verify Conductor is initialized:
32   - Check `conductor/product.md` exists
33   - Check `conductor/tech-stack.md` exists
34   - Check `conductor/workflow.md` exists
35   - If missing: Display error and suggest running `/conductor:setup` first
36 
372. Load context files:
38   - Read `conductor/product.md` for product context
39   - Read `conductor/tech-stack.md` for technical context
40   - Read `conductor/workflow.md` for TDD/commit preferences
41 
42## Track Classification
43 
44Determine track type based on description or ask user:
45 
46```
47What type of track is this?
48 
491. Feature - New functionality
502. Bug - Fix for existing issue
513. Chore - Maintenance, dependencies, config
524. Refactor - Code improvement without behavior change
53```
54 
55## Interactive Specification Gathering
56 
57**CRITICAL RULES:**
58 
59- Ask ONE question per turn
60- Wait for user response before proceeding
61- Tailor questions based on track type
62- Maximum 6 questions total
63 
64### For Feature Tracks
65 
66**Q1: Feature Summary**
67 
68```
69Describe the feature in 1-2 sentences.
70[If argument provided, confirm: "You want to: {argument}. Is this correct?"]
71```
72 
73**Q2: User Story**
74 
75```
76Who benefits and how?
77 
78Format: As a [user type], I want to [action] so that [benefit].
79```
80 
81**Q3: Acceptance Criteria**
82 
83```
84What must be true for this feature to be complete?
85 
86List 3-5 acceptance criteria (one per line):
87```
88 
89**Q4: Dependencies**
90 
91```
92Does this depend on any existing code, APIs, or other tracks?
93 
941. No dependencies
952. Depends on existing code (specify)
963. Depends on incomplete track (specify)
97```
98 
99**Q5: Scope Boundaries**
100 
101```
102What is explicitly OUT of scope for this track?
103(Helps prevent scope creep)
104```
105 
106**Q6: Technical Considerations (optional)**
107 
108```
109Any specific technical approach or constraints?
110(Press enter to skip)
111```
112 
113### For Bug Tracks
114 
115**Q1: Bug Summary**
116 
117```
118What is broken?
119[If argument provided, confirm]
120```
121 
122**Q2: Steps to Reproduce**
123 
124```
125How can this bug be reproduced?
126List steps:
127```
128 
129**Q3: Expected vs Actual Behavior**
130 
131```
132What should happen vs what actually happens?
133```
134 
135**Q4: Affected Areas**
136 
137```
138What parts of the system are affected?
139```
140 
141**Q5: Root Cause Hypothesis (optional)**
142 
143```
144Any hypothesis about the cause?
145(Press enter to skip)
146```
147 
148### For Chore/Refactor Tracks
149 
150**Q1: Task Summary**
151 
152```
153What needs to be done?
154[If argument provided, confirm]
155```
156 
157**Q2: Motivation**
158 
159```
160Why is this work needed?
161```
162 
163**Q3: Success Criteria**
164 
165```
166How will we know this is complete?
167```
168 
169**Q4: Risk Assessment**
170 
171```
172What could go wrong? Any risky changes?
173```
174 
175## Track ID Generation
176 
177Generate track ID in format: `{shortname}_{YYYYMMDD}`
178 
179- Extract shortname from feature/bug summary (2-3 words, lowercase, hyphenated)
180- Use current date
181- Example: `user-auth_20250115`, `nav-bug_20250115`
182 
183Validate uniqueness:
184 
185- Check `conductor/tracks.md` for existing IDs
186- If collision, append counter: `user-auth_20250115_2`
187 
188## Specification Generation
189 
190Create `conductor/tracks/{trackId}/spec.md`:
191 
192```markdown
193# Specification: {Track Title}
194 
195**Track ID:** {trackId}
196**Type:** {Feature|Bug|Chore|Refactor}
197**Created:** {YYYY-MM-DD}
198**Status:** Draft
199 
200## Summary
201 
202{1-2 sentence summary}
203 
204## Context
205 
206{Product context from product.md relevant to this track}
207 
208## User Story (for features)
209 
210As a {user}, I want to {action} so that {benefit}.
211 
212## Problem Description (for bugs)
213 
214{Bug description, steps to reproduce}
215 
216## Acceptance Criteria
217 
218- [ ] {Criterion 1}
219- [ ] {Criterion 2}
220- [ ] {Criterion 3}
221 
222## Dependencies
223 
224{List dependencies or "None"}
225 
226## Out of Scope
227 
228{Explicit exclusions}
229 
230## Technical Notes
231 
232{Technical considerations or "None specified"}
233 
234---
235 
236_Generated by Conductor. Review and edit as needed._
237```
238 
239## User Review of Spec
240 
241Display the generated spec and ask:
242 
243```
244Here is the specification I've generated:
245 
246{spec content}
247 
248Is this specification correct?
2491. Yes, proceed to plan generation
2502. No, let me edit (opens for inline edits)
2513. Start over with different inputs
252```
253 
254## Plan Generation
255 
256After spec approval, generate `conductor/tracks/{trackId}/plan.md`:
257 
258### Plan Structure
259 
260```markdown
261# Implementation Plan: {Track Title}
262 
263**Track ID:** {trackId}
264**Spec:** [spec.md](./spec.md)
265**Created:** {YYYY-MM-DD}
266**Status:** [ ] Not Started
267 
268## Overview
269 
270{Brief summary of implementation approach}
271 
272## Phase 1: {Phase Name}
273 
274{Phase description}
275 
276### Tasks
277 
278- [ ] Task 1.1: {Description}
279- [ ] Task 1.2: {Description}
280- [ ] Task 1.3: {Description}
281 
282### Verification
283 
284- [ ] {Verification step for phase 1}
285 
286## Phase 2: {Phase Name}
287 
288{Phase description}
289 
290### Tasks
291 
292- [ ] Task 2.1: {Description}
293- [ ] Task 2.2: {Description}
294 
295### Verification
296 
297- [ ] {Verification step for phase 2}
298 
299## Phase 3: {Phase Name} (if needed)
300 
301...
302 
303## Final Verification
304 
305- [ ] All acceptance criteria met
306- [ ] Tests passing
307- [ ] Documentation updated (if applicable)
308- [ ] Ready for review
309 
310---
311 
312_Generated by Conductor. Tasks will be marked [~] in progress and [x] complete._
313```
314 
315### Phase Guidelines
316 
317- Group related tasks into logical phases
318- Each phase should be independently verifiable
319- Include verification task after each phase
320- TDD tracks: Include test writing tasks before implementation tasks
321- Typical structure:
322  1. **Setup/Foundation** - Initial scaffolding, interfaces
323  2. **Core Implementation** - Main functionality
324  3. **Integration** - Connect with existing system
325  4. **Polish** - Error handling, edge cases, docs
326 
327## User Review of Plan
328 
329Display the generated plan and ask:
330 
331```
332Here is the implementation plan:
333 
334{plan content}
335 
336Is this plan correct?
3371. Yes, create the track
3382. No, let me edit (opens for inline edits)
3393. Add more phases/tasks
3404. Start over
341```
342 
343## Track Creation
344 
345After plan approval:
346 
3471. Create directory structure:
348 
349   ```
350   conductor/tracks/{trackId}/
351   ├── spec.md
352   ├── plan.md
353   ├── metadata.json
354   └── index.md
355   ```
356 
3572. Create `metadata.json`:
358 
359   ```json
360   {
361     "id": "{trackId}",
362     "title": "{Track Title}",
363     "type": "feature|bug|chore|refactor",
364     "status": "pending",
365     "created": "ISO_TIMESTAMP",
366     "updated": "ISO_TIMESTAMP",
367     "phases": {
368       "total": N,
369       "completed": 0
370     },
371     "tasks": {
372       "total": M,
373       "completed": 0
374     }
375   }
376   ```
377 
3783. Create `index.md`:
379 
380   ```markdown
381   # Track: {Track Title}
382 
383   **ID:** {trackId}
384   **Status:** Pending
385 
386   ## Documents
387 
388   - [Specification](./spec.md)
389   - [Implementation Plan](./plan.md)
390 
391   ## Progress
392 
393   - Phases: 0/{N} complete
394   - Tasks: 0/{M} complete
395 
396   ## Quick Links
397 
398   - [Back to Tracks](../../tracks.md)
399   - [Product Context](../../product.md)
400   ```
401 
4024. Register in `conductor/tracks.md`:
403   - Add row to tracks table
404   - Format: `| [ ] | {trackId} | {title} | {created} | {created} |`
405 
4065. Update `conductor/index.md`:
407   - Add track to "Active Tracks" section
408 
409## Completion Message
410 
411```
412Track created successfully!
413 
414Track ID: {trackId}
415Location: conductor/tracks/{trackId}/
416 
417Files created:
418- spec.md - Requirements specification
419- plan.md - Phased implementation plan
420- metadata.json - Track metadata
421- index.md - Track navigation
422 
423Next steps:
4241. Review spec.md and plan.md, make any edits
4252. Run /conductor:implement {trackId} to start implementation
4263. Run /conductor:status to see project progress
427```
428 
429## Error Handling
430 
431- If directory creation fails: Halt and report, do not register in tracks.md
432- If any file write fails: Clean up partial track, report error
433- If tracks.md update fails: Warn user to manually register track
434