{
  "schema": "https://ai-atoms.com/schemas/skill-v1.json",
  "type": "skill",
  "id": "skill/conductor-setup",
  "version": "1.0.0",
  "name": "Conductor Setup",
  "description": "Initialize project with Conductor artifacts (product definition,",
  "system_prompt_fragment": "# Conductor Setup\n\nInitialize or resume Conductor project setup. This command creates foundational project documentation through interactive Q&A.\n\n## Use this skill when\n\n- Working on conductor setup tasks or workflows\n- Needing guidance, best practices, or checklists for conductor setup\n\n## Do not use this skill when\n\n- The task is unrelated to conductor setup\n- You need a different domain or tool outside this scope\n\n## Instructions\n\n- Clarify goals, constraints, and required inputs.\n- Apply relevant best practices and validate outcomes.\n- Provide actionable steps and verification.\n- If detailed examples are required, open `resources/implementation-playbook.md`.\n\n## Pre-flight Checks\n\n1. Check if `conductor/` directory already exists in the project root:\n   - If `conductor/product.md` exists: Ask user whether to resume setup or reinitialize\n   - If `conductor/setup_state.json` exists with incomplete status: Offer to resume from last step\n\n2. Detect project type by checking for existing indicators:\n   - **Greenfield (new project)**: No .git, no package.json, no requirements.txt, no go.mod, no src/ directory\n   - **Brownfield (existing project)**: Any of the above exist\n\n3. Load or create `conductor/setup_state.json`:\n   ```json\n   {\n     \"status\": \"in_progress\",\n     \"project_type\": \"greenfield|brownfield\",\n     \"current_section\": \"product|guidelines|tech_stack|workflow|styleguides\",\n     \"current_question\": 1,\n     \"completed_sections\": [],\n     \"answers\": {},\n     \"files_created\": [],\n     \"started_at\": \"ISO_TIMESTAMP\",\n     \"last_updated\": \"ISO_TIMESTAMP\"\n   }\n   ```\n\n## Interactive Q&A Protocol\n\n**CRITICAL RULES:**\n\n- Ask ONE question per turn\n- Wait for user response before proceeding\n- Offer 2-3 suggested answers plus \"Type your own\" option\n- Maximum 5 questions per section\n- Update `setup_state.json` after each successful step\n- Validate file writes succeeded before continuing\n\n### Section 1: Product Definition (max 5 questions)\n\n**Q1: Project Name**\n\n```\nWhat is your project name?\n\nSuggested:\n1. [Infer from directory name]\n2. [Infer from package.json/go.mod if brownfield]\n3. Type your own\n```\n\n**Q2: Project Description**\n\n```\nDescribe your project in one sentence.\n\nSuggested:\n1. A web application that [does X]\n2. A CLI tool for [doing Y]\n3. Type your own\n```\n\n**Q3: Problem Statement**\n\n```\nWhat problem does this project solve?\n\nSuggested:\n1. Users struggle to [pain point]\n2. There's no good way to [need]\n3. Type your own\n```\n\n**Q4: Target Users**\n\n```\nWho are the primary users?\n\nSuggested:\n1. Developers building [X]\n2. End users who need [Y]\n3. Internal teams managing [Z]\n4. Type your own\n```\n\n**Q5: Key Goals (optional)**\n\n```\nWhat are 2-3 key goals for this project? (Press enter to skip)\n```\n\n### Section 2: Product Guidelines (max 3 questions)\n\n**Q1: Voice and Tone**\n\n```\nWhat voice/tone should documentation and UI text use?\n\nSuggested:\n1. Professional and technical\n2. Friendly and approachable\n3. Concise and direct\n4. Type your own\n```\n\n**Q2: Design Principles**\n\n```\nWhat design principles guide this project?\n\nSuggested:\n1. Simplicity over features\n2. Performance first\n3. Developer experience focused\n4. User safety and reliability\n5. Type your own (comma-separated)\n```\n\n### Section 3: Tech Stack (max 5 questions)\n\nFor **brownfield projects**, first analyze existing code:\n\n- Run `Glob` to find package.json, requirements.txt, go.mod, Cargo.toml, etc.\n- Parse detected files to pre-populate tech stack\n- Present findings and ask for confirmation/additions\n\n**Q1: Primary Language(s)**\n\n```\nWhat primary language(s) does this project use?\n\n[For brownfield: \"I detected: Python 3.11, JavaScript. Is this correct?\"]\n\nSuggested:\n1. TypeScript\n2. Python\n3. Go\n4. Rust\n5. Type your own (comma-separated)\n```\n\n**Q2: Frontend Framework (if applicable)**\n\n```\nWhat frontend framework (if any)?\n\nSuggested:\n1. React\n2. Vue\n3. Next.js\n4. None / CLI only\n5. Type your own\n```\n\n**Q3: Backend Framework (if applicable)**\n\n```\nWhat backend framework (if any)?\n\nSuggested:\n1. Express / Fastify\n2. Django / FastAPI\n3. Go standard library\n4. None / Frontend only\n5. Type your own\n```\n\n**Q4: Database (if applicable)**\n\n```\nWhat database (if any)?\n\nSuggested:\n1. PostgreSQL\n2. MongoDB\n3. SQLite\n4. None / Stateless\n5. Type your own\n```\n\n**Q5: Infrastructure**\n\n```\nWhere will this be deployed?\n\nSuggested:\n1. AWS (Lambda, ECS, etc.)\n2. Vercel / Netlify\n3. Self-hosted / Docker\n4. Not decided yet\n5. Type your own\n```\n\n### Section 4: Workflow Preferences (max 4 questions)\n\n**Q1: TDD Strictness**\n\n```\nHow strictly should TDD be enforced?\n\nSuggested:\n1. Strict - tests required before implementation\n2. Moderate - tests encouraged, not blocked\n3. Flexible - tests recommended for complex logic\n```\n\n**Q2: Commit Strategy**\n\n```\nWhat commit strategy should be followed?\n\nSuggested:\n1. Conventional Commits (feat:, fix:, etc.)\n2. Descriptive messages, no format required\n3. Squash commits per task\n```\n\n**Q3: Code Review Requirements**\n\n```\nWhat code review policy?\n\nSuggested:\n1. Required for all changes\n2. Required for non-trivial changes\n3. Optional / self-review OK\n```\n\n**Q4: Verification Checkpoints**\n\n```\nWhen should manual verification be required?\n\nSuggested:\n1. After each phase completion\n2. After each task completion\n3. Only at track completion\n```\n\n### Section 5: Code Style Guides (max 2 questions)\n\n**Q1: Languages to Include**\n\n```\nWhich language style guides should be generated?\n\n[Based on detected languages, pre-select]\n\nOptions:\n1. TypeScript/JavaScript\n2. Python\n3. Go\n4. Rust\n5. All detected languages\n6. Skip style guides\n```\n\n**Q2: Existing Conventions**\n\n```\nDo you have existing linting/formatting configs to incorporate?\n\n[For brownfield: \"I found .eslintrc, .prettierrc. Should I incorporate these?\"]\n\nSuggested:\n1. Yes, use existing configs\n2. No, generate fresh guides\n3. Skip this step\n```\n\n## Artifact Generation\n\nAfter completing Q&A, generate the following files:\n\n### 1. conductor/index.md\n\n```markdown\n# Conductor - [Project Name]\n\nNavigation hub for project context.\n\n## Quick Links\n\n- Product Definition\n- Product Guidelines\n- Tech Stack\n- Workflow\n- Tracks\n\n## Active Tracks\n\n<!-- Auto-populated by /conductor:new-track -->\n\n## Getting Started\n\nRun `/conductor:new-track` to create your first feature track.\n```\n\n### 2. conductor/product.md\n\nTemplate populated with Q&A answers for:\n\n- Project name and description\n- Problem statement\n- Target users\n- Key goals\n\n### 3. conductor/product-guidelines.md\n\nTemplate populated with:\n\n- Voice and tone\n- Design principles\n- Any additional standards\n\n### 4. conductor/tech-stack.md\n\nTemplate populated with:\n\n- Languages (with versions if detected)\n- Frameworks (frontend, backend)\n- Database\n- Infrastructure\n- Key dependencies (for brownfield, from package files)\n\n### 5. conductor/workflow.md\n\nTemplate populated with:\n\n- TDD policy and strictness level\n- Commit strategy and conventions\n- Code review requirements\n- Verification checkpoint rules\n- Task lifecycle definition\n\n### 6. conductor/tracks.md\n\n```markdown\n# Tracks Registry\n\n| Status | Track ID | Title | Created | Updated |\n| ------ | -------- | ----- | ------- | ------- |\n\n<!-- Tracks registered by /conductor:new-track -->\n```\n\n### 7. conductor/code_styleguides/\n\nGenerate selected style guides from `$CLAUDE_PLUGIN_ROOT/templates/code_styleguides/`\n\n## State Management\n\nAfter each successful file creation:\n\n1. Update `setup_state.json`:\n   - Add filename to `files_created` array\n   - Update `last_updated` timestamp\n   - If section complete, add to `completed_sections`\n2. Verify file exists with `Read` tool\n\n## Completion\n\nWhen all files are created:\n\n1. Set `setup_state.json` status to \"complete\"\n2. Display summary:\n\n   ```\n   Conductor setup complete!\n\n   Created artifacts:\n   - conductor/index.md\n   - conductor/product.md\n   - conductor/product-guidelines.md\n   - conductor/tech-stack.md\n   - conductor/workflow.md\n   - conductor/tracks.md\n   - conductor/code_styleguides/[languages]\n\n   Next steps:\n   1. Review generated files and customize as needed\n   2. Run /conductor:new-track to create your first track\n   ```\n\n## Resume Handling\n\nIf `--resume` argument or resuming from state:\n\n1. Load `setup_state.json`\n2. Skip completed sections\n3. Resume from `current_section` and `current_question`\n4. Verify previously created files still exist\n5. If files missing, offer to regenerate\n\n## Error Handling\n\n- If file write fails: Halt and report error, do not update state\n- If user cancels: Save current state for future resume\n- If state file corrupted: Offer to start fresh or attempt recovery",
  "applicable_domains": [
    "other"
  ],
  "category": "other",
  "invocation": [
    "/conductor-setup"
  ],
  "authored_by": "claudeskills.in community",
  "source_url": "https://claudeskills.in/skill/conductor-setup",
  "provenance": {
    "source": "claudeskills.in",
    "source_url": "https://claudeskills.in/skill/conductor-setup",
    "license": "unknown",
    "imported_at": "2026-09-03",
    "notes": "Aggregated by claudeskills.in from community GitHub lists."
  },
  "tags": [
    "claudeskills",
    "other"
  ],
  "lifecycle": "draft"
}