mcpbeat Sign in

Conductor Setup Agent Skill

Initialize project with Conductor artifacts (product definition, tech stack, workflow, style guides)

3k tokens
context cost
the whole folder, loaded on every use
13
files
instructions only
0
copies elsewhere
how many repositories repackaged it
505
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/Dokhacgiakhoa/Agent-Skills-4-Vibe-Coding-CLI --skill conductor-setup

What comes with it

6 737 bytes besides the instruction
sub-skills/1-conductorindexmd.md
sub-skills/2-conductorproductmd.md
sub-skills/3-conductorproduct-guidelinesmd.md
sub-skills/4-conductortech-stackmd.md
sub-skills/5-conductorworkflowmd.md
sub-skills/6-conductortracksmd.md
sub-skills/7-conductorcode_styleguides.md
sub-skills/section-1-product-definition-max-5-questions.md
sub-skills/section-2-product-guidelines-max-3-questions.md
sub-skills/section-3-tech-stack-max-5-questions.md
sub-skills/section-4-workflow-preferences-max-4-questions.md
sub-skills/section-5-code-style-guides-max-2-questions.md

The instruction itself

19 sections, as written by the author

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.md exists: Ask user whether to resume setup or reinitialize
  • If conductor/setup_state.json exists with incomplete status: Offer to resume from last step
  • 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.json after each successful step
  • Validate file writes succeeded before continuing

🧠 Knowledge Modules (Fractal Skills)

1. Section 1: Product Definition (max 5 questions)

2. Section 2: Product Guidelines (max 3 questions)

3. Section 3: Tech Stack (max 5 questions)

4. Section 4: Workflow Preferences (max 4 questions)

5. Section 5: Code Style Guides (max 2 questions)

6. 1. conductor/index.md

7. 2. conductor/product.md

8. 3. conductor/product-guidelines.md

9. 4. conductor/tech-stack.md

10. 5. conductor/workflow.md

11. 6. conductor/tracks.md

12. 7. conductor/code_styleguides/

Other skills for the same job

different authors, same section of the catalogue
Doc Coauthoring
by anthropics
vendor ×10

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

4k tokens
File Organizer
by frostant
×10

Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.

3k tokens
Domain Name Brainstormer
by frostant
×8

Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.

1k tokens
Brainstorming
by ZhanlinCui
×4

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

626 tokens
Planning With Files
by ZhanlinCui
×3

Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.

9k tokens scripts
Scientific Brainstorming
by christophacham
×3

Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.

5k tokens
GitHub Project Management
by ComeOnOliver
×3

Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning

14k tokens
Grill Me
by ComeOnOliver
×3

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

3k tokens

How to use it

Copy the folder

Take dokhacgiakhoa/conductor-setup from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.