Conductor Setup

1---
2name: conductor-setup
3description: Initialize project with Conductor artifacts (product definition,
4  tech stack, workflow, style guides)
5metadata:
6  argument-hint: "[--resume]"
7---
8 
9# Conductor Setup
10 
11Initialize or resume Conductor project setup. This command creates foundational project documentation through interactive Q&A.
12 
13## Use this skill when
14 
15- Working on conductor setup tasks or workflows
16- Needing guidance, best practices, or checklists for conductor setup
17 
18## Do not use this skill when
19 
20- The task is unrelated to conductor setup
21- You need a different domain or tool outside this scope
22 
23## Instructions
24 
25- Clarify goals, constraints, and required inputs.
26- Apply relevant best practices and validate outcomes.
27- Provide actionable steps and verification.
28- If detailed examples are required, open `resources/implementation-playbook.md`.
29 
30## Pre-flight Checks
31 
321. Check if `conductor/` directory already exists in the project root:
33   - If `conductor/product.md` exists: Ask user whether to resume setup or reinitialize
34   - If `conductor/setup_state.json` exists with incomplete status: Offer to resume from last step
35 
362. Detect project type by checking for existing indicators:
37   - **Greenfield (new project)**: No .git, no package.json, no requirements.txt, no go.mod, no src/ directory
38   - **Brownfield (existing project)**: Any of the above exist
39 
403. Load or create `conductor/setup_state.json`:
41   ```json
42   {
43     "status": "in_progress",
44     "project_type": "greenfield|brownfield",
45     "current_section": "product|guidelines|tech_stack|workflow|styleguides",
46     "current_question": 1,
47     "completed_sections": [],
48     "answers": {},
49     "files_created": [],
50     "started_at": "ISO_TIMESTAMP",
51     "last_updated": "ISO_TIMESTAMP"
52   }
53   ```
54 
55## Interactive Q&A Protocol
56 
57**CRITICAL RULES:**
58 
59- Ask ONE question per turn
60- Wait for user response before proceeding
61- Offer 2-3 suggested answers plus "Type your own" option
62- Maximum 5 questions per section
63- Update `setup_state.json` after each successful step
64- Validate file writes succeeded before continuing
65 
66### Section 1: Product Definition (max 5 questions)
67 
68**Q1: Project Name**
69 
70```
71What is your project name?
72 
73Suggested:
741. [Infer from directory name]
752. [Infer from package.json/go.mod if brownfield]
763. Type your own
77```
78 
79**Q2: Project Description**
80 
81```
82Describe your project in one sentence.
83 
84Suggested:
851. A web application that [does X]
862. A CLI tool for [doing Y]
873. Type your own
88```
89 
90**Q3: Problem Statement**
91 
92```
93What problem does this project solve?
94 
95Suggested:
961. Users struggle to [pain point]
972. There's no good way to [need]
983. Type your own
99```
100 
101**Q4: Target Users**
102 
103```
104Who are the primary users?
105 
106Suggested:
1071. Developers building [X]
1082. End users who need [Y]
1093. Internal teams managing [Z]
1104. Type your own
111```
112 
113**Q5: Key Goals (optional)**
114 
115```
116What are 2-3 key goals for this project? (Press enter to skip)
117```
118 
119### Section 2: Product Guidelines (max 3 questions)
120 
121**Q1: Voice and Tone**
122 
123```
124What voice/tone should documentation and UI text use?
125 
126Suggested:
1271. Professional and technical
1282. Friendly and approachable
1293. Concise and direct
1304. Type your own
131```
132 
133**Q2: Design Principles**
134 
135```
136What design principles guide this project?
137 
138Suggested:
1391. Simplicity over features
1402. Performance first
1413. Developer experience focused
1424. User safety and reliability
1435. Type your own (comma-separated)
144```
145 
146### Section 3: Tech Stack (max 5 questions)
147 
148For **brownfield projects**, first analyze existing code:
149 
150- Run `Glob` to find package.json, requirements.txt, go.mod, Cargo.toml, etc.
151- Parse detected files to pre-populate tech stack
152- Present findings and ask for confirmation/additions
153 
154**Q1: Primary Language(s)**
155 
156```
157What primary language(s) does this project use?
158 
159[For brownfield: "I detected: Python 3.11, JavaScript. Is this correct?"]
160 
161Suggested:
1621. TypeScript
1632. Python
1643. Go
1654. Rust
1665. Type your own (comma-separated)
167```
168 
169**Q2: Frontend Framework (if applicable)**
170 
171```
172What frontend framework (if any)?
173 
174Suggested:
1751. React
1762. Vue
1773. Next.js
1784. None / CLI only
1795. Type your own
180```
181 
182**Q3: Backend Framework (if applicable)**
183 
184```
185What backend framework (if any)?
186 
187Suggested:
1881. Express / Fastify
1892. Django / FastAPI
1903. Go standard library
1914. None / Frontend only
1925. Type your own
193```
194 
195**Q4: Database (if applicable)**
196 
197```
198What database (if any)?
199 
200Suggested:
2011. PostgreSQL
2022. MongoDB
2033. SQLite
2044. None / Stateless
2055. Type your own
206```
207 
208**Q5: Infrastructure**
209 
210```
211Where will this be deployed?
212 
213Suggested:
2141. AWS (Lambda, ECS, etc.)
2152. Vercel / Netlify
2163. Self-hosted / Docker
2174. Not decided yet
2185. Type your own
219```
220 
221### Section 4: Workflow Preferences (max 4 questions)
222 
223**Q1: TDD Strictness**
224 
225```
226How strictly should TDD be enforced?
227 
228Suggested:
2291. Strict - tests required before implementation
2302. Moderate - tests encouraged, not blocked
2313. Flexible - tests recommended for complex logic
232```
233 
234**Q2: Commit Strategy**
235 
236```
237What commit strategy should be followed?
238 
239Suggested:
2401. Conventional Commits (feat:, fix:, etc.)
2412. Descriptive messages, no format required
2423. Squash commits per task
243```
244 
245**Q3: Code Review Requirements**
246 
247```
248What code review policy?
249 
250Suggested:
2511. Required for all changes
2522. Required for non-trivial changes
2533. Optional / self-review OK
254```
255 
256**Q4: Verification Checkpoints**
257 
258```
259When should manual verification be required?
260 
261Suggested:
2621. After each phase completion
2632. After each task completion
2643. Only at track completion
265```
266 
267### Section 5: Code Style Guides (max 2 questions)
268 
269**Q1: Languages to Include**
270 
271```
272Which language style guides should be generated?
273 
274[Based on detected languages, pre-select]
275 
276Options:
2771. TypeScript/JavaScript
2782. Python
2793. Go
2804. Rust
2815. All detected languages
2826. Skip style guides
283```
284 
285**Q2: Existing Conventions**
286 
287```
288Do you have existing linting/formatting configs to incorporate?
289 
290[For brownfield: "I found .eslintrc, .prettierrc. Should I incorporate these?"]
291 
292Suggested:
2931. Yes, use existing configs
2942. No, generate fresh guides
2953. Skip this step
296```
297 
298## Artifact Generation
299 
300After completing Q&A, generate the following files:
301 
302### 1. conductor/index.md
303 
304```markdown
305# Conductor - [Project Name]
306 
307Navigation hub for project context.
308 
309## Quick Links
310 
311- [Product Definition](./product.md)
312- [Product Guidelines](./product-guidelines.md)
313- [Tech Stack](./tech-stack.md)
314- [Workflow](./workflow.md)
315- [Tracks](./tracks.md)
316 
317## Active Tracks
318 
319<!-- Auto-populated by /conductor:new-track -->
320 
321## Getting Started
322 
323Run `/conductor:new-track` to create your first feature track.
324```
325 
326### 2. conductor/product.md
327 
328Template populated with Q&A answers for:
329 
330- Project name and description
331- Problem statement
332- Target users
333- Key goals
334 
335### 3. conductor/product-guidelines.md
336 
337Template populated with:
338 
339- Voice and tone
340- Design principles
341- Any additional standards
342 
343### 4. conductor/tech-stack.md
344 
345Template populated with:
346 
347- Languages (with versions if detected)
348- Frameworks (frontend, backend)
349- Database
350- Infrastructure
351- Key dependencies (for brownfield, from package files)
352 
353### 5. conductor/workflow.md
354 
355Template populated with:
356 
357- TDD policy and strictness level
358- Commit strategy and conventions
359- Code review requirements
360- Verification checkpoint rules
361- Task lifecycle definition
362 
363### 6. conductor/tracks.md
364 
365```markdown
366# Tracks Registry
367 
368| Status | Track ID | Title | Created | Updated |
369| ------ | -------- | ----- | ------- | ------- |
370 
371<!-- Tracks registered by /conductor:new-track -->
372```
373 
374### 7. conductor/code_styleguides/
375 
376Generate selected style guides from `$CLAUDE_PLUGIN_ROOT/templates/code_styleguides/`
377 
378## State Management
379 
380After each successful file creation:
381 
3821. Update `setup_state.json`:
383   - Add filename to `files_created` array
384   - Update `last_updated` timestamp
385   - If section complete, add to `completed_sections`
3862. Verify file exists with `Read` tool
387 
388## Completion
389 
390When all files are created:
391 
3921. Set `setup_state.json` status to "complete"
3932. Display summary:
394 
395   ```
396   Conductor setup complete!
397 
398   Created artifacts:
399   - conductor/index.md
400   - conductor/product.md
401   - conductor/product-guidelines.md
402   - conductor/tech-stack.md
403   - conductor/workflow.md
404   - conductor/tracks.md
405   - conductor/code_styleguides/[languages]
406 
407   Next steps:
408   1. Review generated files and customize as needed
409   2. Run /conductor:new-track to create your first track
410   ```
411 
412## Resume Handling
413 
414If `--resume` argument or resuming from state:
415 
4161. Load `setup_state.json`
4172. Skip completed sections
4183. Resume from `current_section` and `current_question`
4194. Verify previously created files still exist
4205. If files missing, offer to regenerate
421 
422## Error Handling
423 
424- If file write fails: Halt and report error, do not update state
425- If user cancels: Save current state for future resume
426- If state file corrupted: Offer to start fresh or attempt recovery
427