Conductor Setup
conductor-setup
Initialize project with Conductor artifacts (product definition,
SKILL.md
Full skill instructions
Conductor Setup
Initialize or resume Conductor project setup. This command creates foundational project documentation through interactive Q&A.
Use this skill when
- Working on conductor setup tasks or workflows
- Needing guidance, best practices, or checklists for conductor setup
Do not use this skill when
- The task is unrelated to conductor setup
- 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
-
Check if
conductor/directory already exists in the project root:- If
conductor/product.mdexists: Ask user whether to resume setup or reinitialize - If
conductor/setup_state.jsonexists with incomplete status: Offer to resume from last step
- If
-
Detect project type by checking for existing indicators:
- Greenfield (new project): No .git, no package.json, no requirements.txt, no go.mod, no src/ directory
- Brownfield (existing project): Any of the above exist
-
Load or create
conductor/setup_state.json:{ "status": "in_progress", "project_type": "greenfield|brownfield", "current_section": "product|guidelines|tech_stack|workflow|styleguides", "current_question": 1, "completed_sections": [], "answers": {}, "files_created": [], "started_at": "ISO_TIMESTAMP", "last_updated": "ISO_TIMESTAMP" }
Interactive Q&A Protocol
CRITICAL RULES:
- Ask ONE question per turn
- Wait for user response before proceeding
- Offer 2-3 suggested answers plus "Type your own" option
- Maximum 5 questions per section
- Update
setup_state.jsonafter each successful step - Validate file writes succeeded before continuing
