Back to Details

conductor-setup

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Conductor Setup

Conductor 项目初始化

Initialize or resume Conductor project setup. This command creates foundational project documentation through interactive Q&A.
初始化或恢复Conductor项目的配置流程。该命令通过交互式问答创建项目基础文档。

Use this skill when

适用场景

  • Working on conductor setup tasks or workflows
  • Needing guidance, best practices, or checklists for conductor setup
  • 进行Conductor项目初始化任务或工作流配置时
  • 需要Conductor项目初始化的指导、最佳实践或检查清单时

Do not use this skill when

不适用场景

  • The task is unrelated to conductor setup
  • You need a different domain or tool outside this scope
  • 任务与Conductor项目初始化无关时
  • 需要该范围之外的其他领域或工具支持时

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
    .
  • 明确目标、约束条件和所需输入。
  • 应用相关最佳实践并验证结果。
  • 提供可执行步骤和验证方法。
  • 如果需要详细示例，请打开
    resources/implementation-playbook.md
    。

Pre-flight Checks

前期检查

  1. 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
  2. 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
  3. Load or create 
    conductor/setup_state.json
    :
    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"
}
  1. 检查项目根目录是否已存在
    conductor/
    文件夹：
    • 若
      conductor/product.md
      已存在：询问用户是恢复配置还是重新初始化
    • 若存在状态未完成的
      conductor/setup_state.json
      ：提供从上次步骤恢复的选项
  2. 通过现有标识检测项目类型：
    • 全新项目（Greenfield）：无.git、package.json、requirements.txt、go.mod或src/目录
    • 存量项目（Brownfield）：存在上述任意文件或目录
  3. 加载或创建
    conductor/setup_state.json
    ：
    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
核心规则：
  • 每次仅提出一个问题
  • 等待用户回复后再继续
  • 提供2-3个建议答案及“自定义输入”选项
  • 每个模块最多5个问题
  • 每完成一个步骤后更新
    setup_state.json
  • 继续前验证文件写入是否成功

Section 1: Product Definition (max 5 questions)

模块1：产品定义（最多5个问题）

Q1: Project Name
What is your project name?

Suggested:
1. [Infer from directory name]
2. [Infer from package.json/go.mod if brownfield]
3. Type your own
Q2: Project Description
Describe your project in one sentence.

Suggested:
1. A web application that [does X]
2. A CLI tool for [doing Y]
3. Type your own
Q3: Problem Statement
What problem does this project solve?

Suggested:
1. Users struggle to [pain point]
2. There's no good way to [need]
3. Type your own
Q4: Target Users
Who are the primary users?

Suggested:
1. Developers building [X]
2. End users who need [Y]
3. Internal teams managing [Z]
4. Type your own
Q5: Key Goals (optional)
What are 2-3 key goals for this project? (Press enter to skip)
问题1：项目名称
请输入您的项目名称：

建议选项：
1. [从目录名推断]
2. [若为存量项目，从package.json/go.mod推断]
3. 自定义输入
问题2：项目描述
请用一句话描述您的项目：

建议选项：
1. 一款[实现X功能]的Web应用
2. 一款用于[完成Y操作]的CLI工具
3. 自定义输入
问题3：问题陈述
该项目解决了什么问题？

建议选项：
1. 用户在[某痛点]上存在困扰
2. 目前缺乏[某需求]的解决方案
3. 自定义输入
问题4：目标用户
主要目标用户群体是？

建议选项：
1. 开发[X产品]的开发者
2. 需要[Y功能]的终端用户
3. 管理[Z业务]的内部团队
4. 自定义输入
问题5：核心目标（可选）
请列出该项目的2-3个核心目标：（按回车可跳过）

Section 2: Product Guidelines (max 3 questions)

模块2：产品规范（最多3个问题）

Q1: Voice and Tone
What voice/tone should documentation and UI text use?

Suggested:
1. Professional and technical
2. Friendly and approachable
3. Concise and direct
4. Type your own
Q2: Design Principles
What design principles guide this project?

Suggested:
1. Simplicity over features
2. Performance first
3. Developer experience focused
4. User safety and reliability
5. Type your own (comma-separated)
问题1：语气风格
文档和UI文本应采用何种语气风格？

建议选项：
1. 专业技术风
2. 友好亲切风
3. 简洁直接风
4. 自定义输入
问题2：设计原则
该项目遵循哪些设计原则？

建议选项：
1. 简洁优先于功能
2. 性能优先
3. 聚焦开发者体验
4. 用户安全与可靠性
5. 自定义输入（逗号分隔）

Section 3: Tech Stack (max 5 questions)

模块3：技术栈（最多5个问题）

For brownfield projects, first analyze existing code:
  • Run 
    Glob
    to find package.json, requirements.txt, go.mod, Cargo.toml, etc.
  • Parse detected files to pre-populate tech stack
  • Present findings and ask for confirmation/additions
Q1: Primary Language(s)
What primary language(s) does this project use?

[For brownfield: "I detected: Python 3.11, JavaScript. Is this correct?"]

Suggested:
1. TypeScript
2. Python
3. Go
4. Rust
5. Type your own (comma-separated)
Q2: Frontend Framework (if applicable)
What frontend framework (if any)?

Suggested:
1. React
2. Vue
3. Next.js
4. None / CLI only
5. Type your own
Q3: Backend Framework (if applicable)
What backend framework (if any)?

Suggested:
1. Express / Fastify
2. Django / FastAPI
3. Go standard library
4. None / Frontend only
5. Type your own
Q4: Database (if applicable)
What database (if any)?

Suggested:
1. PostgreSQL
2. MongoDB
3. SQLite
4. None / Stateless
5. Type your own
Q5: Infrastructure
Where will this be deployed?

Suggested:
1. AWS (Lambda, ECS, etc.)
2. Vercel / Netlify
3. Self-hosted / Docker
4. Not decided yet
5. Type your own
对于存量项目，首先分析现有代码：
  • 运行
    Glob
    查找package.json、requirements.txt、go.mod、Cargo.toml等文件
  • 解析检测到的文件以预填充技术栈信息
  • 展示检测结果并询问用户确认或补充
问题1：主要开发语言
该项目使用的主要开发语言是？

[若为存量项目：“我检测到：Python 3.11、JavaScript。是否正确？”]

建议选项：
1. TypeScript
2. Python
3. Go
4. Rust
5. 自定义输入（逗号分隔）
问题2：前端框架（如适用）
使用的前端框架是（如无则选“无”）？

建议选项：
1. React
2. Vue
3. Next.js
4. 无 / 仅CLI工具
5. 自定义输入
问题3：后端框架（如适用）
使用的后端框架是（如无则选“无”）？

建议选项：
1. Express / Fastify
2. Django / FastAPI
3. Go标准库
4. 无 / 仅前端项目
5. 自定义输入
问题4：数据库（如适用）
使用的数据库是（如无则选“无”）？

建议选项：
1. PostgreSQL
2. MongoDB
3. SQLite
4. 无 / 无状态服务
5. 自定义输入
问题5：基础设施
项目将部署在何处？

建议选项：
1. AWS（Lambda、ECS等）
2. Vercel / Netlify
3. 自建服务器 / Docker
4. 尚未确定
5. 自定义输入

Section 4: Workflow Preferences (max 4 questions)

模块4：工作流偏好（最多4个问题）

Q1: TDD Strictness
How strictly should TDD be enforced?

Suggested:
1. Strict - tests required before implementation
2. Moderate - tests encouraged, not blocked
3. Flexible - tests recommended for complex logic
Q2: Commit Strategy
What commit strategy should be followed?

Suggested:
1. Conventional Commits (feat:, fix:, etc.)
2. Descriptive messages, no format required
3. Squash commits per task
Q3: Code Review Requirements
What code review policy?

Suggested:
1. Required for all changes
2. Required for non-trivial changes
3. Optional / self-review OK
Q4: Verification Checkpoints
When should manual verification be required?

Suggested:
1. After each phase completion
2. After each task completion
3. Only at track completion
问题1：TDD严格程度
TDD（测试驱动开发）的执行严格程度是？

建议选项：
1. 严格要求 - 实现前必须编写测试
2. 中等要求 - 鼓励编写测试，但不强制
3. 灵活要求 - 仅建议为复杂逻辑编写测试
问题2：提交策略
应遵循何种代码提交策略？

建议选项：
1. Conventional Commits（feat:、fix:等规范）
2. 描述性消息，无格式要求
3. 按任务合并提交
问题3：代码评审要求
代码评审政策是？

建议选项：
1. 所有变更均需评审
2. 非琐碎变更需评审
3. 可选 / 允许自评审
问题4：验证检查点
何时需要进行人工验证？

建议选项：
1. 每个阶段完成后
2. 每个任务完成后
3. 仅在整个流程完成后

Section 5: Code Style Guides (max 2 questions)

模块5：代码风格指南（最多2个问题）

Q1: Languages to Include
Which language style guides should be generated?

[Based on detected languages, pre-select]

Options:
1. TypeScript/JavaScript
2. Python
3. Go
4. Rust
5. All detected languages
6. Skip style guides
Q2: Existing Conventions
Do you have existing linting/formatting configs to incorporate?

[For brownfield: "I found .eslintrc, .prettierrc. Should I incorporate these?"]

Suggested:
1. Yes, use existing configs
2. No, generate fresh guides
3. Skip this step
问题1：需包含的语言
需要生成哪些语言的风格指南？

[基于检测到的语言自动预选]

选项：
1. TypeScript/JavaScript
2. Python
3. Go
4. Rust
5. 所有检测到的语言
6. 跳过风格指南生成
问题2：现有规范
是否需要整合已有的代码检查/格式化配置？

[若为存量项目：“我发现了.eslintrc、.prettierrc文件。是否需要整合这些配置？”]

建议选项：
1. 是，使用现有配置
2. 否，生成全新指南
3. 跳过此步骤

Artifact Generation

工件生成

After completing Q&A, generate the following files:
完成问答后，将生成以下文件：

1. conductor/index.md

1. conductor/index.md

markdown
undefined
markdown
undefined

Conductor - [Project Name]

Conductor - [项目名称]

Navigation hub for project context.
项目上下文导航中心

Quick Links

快速链接

  • Product Definition
  • Product Guidelines
  • Tech Stack
  • Workflow
  • Tracks
  • 产品定义
  • 产品规范
  • 技术栈
  • 工作流
  • 任务跟踪

Active Tracks

活跃任务跟踪

<!-- Auto-populated by /conductor:new-track -->
<!-- 由/conductor:new-track自动填充 -->

Getting Started

快速开始

Run 
/conductor:new-track
to create your first feature track.
undefined
运行
/conductor:new-track
创建您的第一个功能任务跟踪
undefined

2. conductor/product.md

2. conductor/product.md

Template populated with Q&A answers for:
  • Project name and description
  • Problem statement
  • Target users
  • Key goals
填充问答结果的模板，包含：
  • 项目名称与描述
  • 问题陈述
  • 目标用户
  • 核心目标

3. conductor/product-guidelines.md

3. conductor/product-guidelines.md

Template populated with:
  • Voice and tone
  • Design principles
  • Any additional standards
填充内容的模板，包含：
  • 语气风格
  • 设计原则
  • 其他附加标准

4. conductor/tech-stack.md

4. conductor/tech-stack.md

Template populated with:
  • Languages (with versions if detected)
  • Frameworks (frontend, backend)
  • Database
  • Infrastructure
  • Key dependencies (for brownfield, from package files)
填充内容的模板，包含：
  • 开发语言（若检测到则包含版本）
  • 框架（前端、后端）
  • 数据库
  • 基础设施
  • 核心依赖（存量项目从包文件提取）

5. conductor/workflow.md

5. conductor/workflow.md

Template populated with:
  • TDD policy and strictness level
  • Commit strategy and conventions
  • Code review requirements
  • Verification checkpoint rules
  • Task lifecycle definition
填充内容的模板，包含：
  • TDD政策与严格程度
  • 提交策略与规范
  • 代码评审要求
  • 验证检查点规则
  • 任务生命周期定义

6. conductor/tracks.md

6. conductor/tracks.md

markdown
undefined
markdown
undefined

Tracks Registry

任务跟踪注册表

StatusTrack IDTitleCreatedUpdated
<!-- Tracks registered by /conductor:new-track --> 
undefined
状态跟踪ID标题创建时间更新时间
<!-- 由/conductor:new-track注册的任务跟踪 --> 
undefined

7. conductor/code_styleguides/

7. conductor/code_styleguides/

Generate selected style guides from 
$CLAUDE_PLUGIN_ROOT/templates/code_styleguides/
从
$CLAUDE_PLUGIN_ROOT/templates/code_styleguides/
生成选中的风格指南

State Management

状态管理

After each successful file creation:
  1. Update 
    setup_state.json
    :
    • Add filename to 
      files_created
      array
    • Update 
      last_updated
      timestamp
    • If section complete, add to 
      completed_sections
  2. Verify file exists with 
    Read
    tool
每次成功创建文件后：
  1. 更新
    setup_state.json
    ：
    • 将文件名添加至
      files_created
      数组
    • 更新
      last_updated
      时间戳
    • 若模块完成，将其添加至
      completed_sections
  2. 使用
    Read
    工具验证文件是否存在

Completion

完成阶段

When all files are created:
  1. Set 
    setup_state.json
    status to "complete"
  2. Display summary:
    Conductor setup complete!

Created artifacts:
- conductor/index.md
- conductor/product.md
- conductor/product-guidelines.md
- conductor/tech-stack.md
- conductor/workflow.md
- conductor/tracks.md
- conductor/code_styleguides/[languages]

Next steps:
1. Review generated files and customize as needed
2. Run /conductor:new-track to create your first track
所有文件创建完成后：
  1. 将
    setup_state.json
    的状态设置为"complete"
  2. 显示总结信息：
    Conductor项目初始化完成！

已创建的工件：
- conductor/index.md
- conductor/product.md
- conductor/product-guidelines.md
- conductor/tech-stack.md
- conductor/workflow.md
- conductor/tracks.md
- conductor/code_styleguides/[对应语言]

下一步操作：
1. 查看生成的文件并按需自定义
2. 运行/conductor:new-track创建您的第一个任务跟踪

Resume Handling

恢复机制

If 
--resume
argument or resuming from state:
  1. Load 
    setup_state.json
  2. Skip completed sections
  3. Resume from 
    current_section
    and 
    current_question
  4. Verify previously created files still exist
  5. If files missing, offer to regenerate
若使用
--resume
参数或从现有状态恢复：
  1. 加载
    setup_state.json
  2. 跳过已完成的模块
  3. 从
    current_section
    和
    current_question
    恢复
  4. 验证之前创建的文件是否仍存在
  5. 若文件丢失，提供重新生成选项

Error Handling

错误处理

  • If file write fails: Halt and report error, do not update state
  • If user cancels: Save current state for future resume
  • If state file corrupted: Offer to start fresh or attempt recovery
  • 若文件写入失败：暂停操作并报告错误，不更新状态
  • 若用户取消操作：保存当前状态以便后续恢复
  • 若状态文件损坏：提供重新开始或尝试恢复的选项