conductor-new-track

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

New Track

新Track

Create a new track (feature, bug fix, chore, or refactor) with a detailed specification and phased implementation plan.

创建带有详细规格说明和分阶段实施计划的新Track（功能、Bug修复、杂务或重构）。

Use this skill when

何时使用此技能

Working on new track tasks or workflows
Needing guidance, best practices, or checklists for new track

处理新Track任务或工作流时
需要新Track相关的指导、最佳实践或检查清单时

Do not use this skill when

何时不使用此技能

The task is unrelated to new track
You need a different domain or tool outside this scope

任务与新Track无关时
需要此范围之外的其他领域或工具时

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

预检查

Verify Conductor is initialized:
- Check
```
conductor/product.md
```
  exists
- Check
```
conductor/tech-stack.md
```
  exists
- Check
```
conductor/workflow.md
```
  exists
- If missing: Display error and suggest running
```
/conductor:setup
```
  first
Load context files:
- Read
```
conductor/product.md
```
  for product context
- Read
```
conductor/tech-stack.md
```
  for technical context
- Read
```
conductor/workflow.md
```
  for TDD/commit preferences

验证Conductor已初始化：
- 检查
```
conductor/product.md
```
  是否存在
- 检查
```
conductor/tech-stack.md
```
  是否存在
- 检查
```
conductor/workflow.md
```
  是否存在
- 如果缺失：显示错误并建议先运行
```
/conductor:setup
```
加载上下文文件：
- 读取
```
conductor/product.md
```
  获取产品上下文
- 读取
```
conductor/tech-stack.md
```
  获取技术上下文
- 读取
```
conductor/workflow.md
```
  获取TDD/提交偏好

Track Classification

Track分类

Determine track type based on description or ask user:

What type of track is this?

1. Feature - New functionality
2. Bug - Fix for existing issue
3. Chore - Maintenance, dependencies, config
4. Refactor - Code improvement without behavior change

根据描述确定Track类型，或询问用户：

What type of track is this?

1. Feature - New functionality
2. Bug - Fix for existing issue
3. Chore - Maintenance, dependencies, config
4. Refactor - Code improvement without behavior change

Interactive Specification Gathering

交互式规格说明收集

CRITICAL RULES:

Ask ONE question per turn
Wait for user response before proceeding
Tailor questions based on track type
Maximum 6 questions total

重要规则：

每次只提一个问题
等待用户回复后再继续
根据Track类型调整问题
最多总共6个问题

For Feature Tracks

针对功能类Track

Q1: Feature Summary

Describe the feature in 1-2 sentences.
[If argument provided, confirm: "You want to: {argument}. Is this correct?"]

Q2: User Story

Who benefits and how?

Format: As a [user type], I want to [action] so that [benefit].

Q3: Acceptance Criteria

What must be true for this feature to be complete?

List 3-5 acceptance criteria (one per line):

Q4: Dependencies

Does this depend on any existing code, APIs, or other tracks?

1. No dependencies
2. Depends on existing code (specify)
3. Depends on incomplete track (specify)

Q5: Scope Boundaries

What is explicitly OUT of scope for this track?
(Helps prevent scope creep)

Q6: Technical Considerations (optional)

Any specific technical approach or constraints?
(Press enter to skip)

Q1: 功能摘要

Describe the feature in 1-2 sentences.
[If argument provided, confirm: "You want to: {argument}. Is this correct?"]

Q2: 用户故事

Who benefits and how?

Format: As a [user type], I want to [action] so that [benefit].

Q3: 验收标准

What must be true for this feature to be complete?

List 3-5 acceptance criteria (one per line):

Q4: 依赖项

Does this depend on any existing code, APIs, or other tracks?

1. No dependencies
2. Depends on existing code (specify)
3. Depends on incomplete track (specify)

Q5: 范围边界

What is explicitly OUT of scope for this track?
(Helps prevent scope creep)

Q6: 技术考量（可选）

Any specific technical approach or constraints?
(Press enter to skip)

For Bug Tracks

针对Bug类Track

Q1: Bug Summary

What is broken?
[If argument provided, confirm]

Q2: Steps to Reproduce

How can this bug be reproduced?
List steps:

Q3: Expected vs Actual Behavior

What should happen vs what actually happens?

Q4: Affected Areas

What parts of the system are affected?

Q5: Root Cause Hypothesis (optional)

Any hypothesis about the cause?
(Press enter to skip)

Q1: Bug摘要

What is broken?
[If argument provided, confirm]

Q2: 复现步骤

How can this bug be reproduced?
List steps:

Q3: 预期与实际行为

What should happen vs what actually happens?

Q4: 影响范围

What parts of the system are affected?

Q5: 根因假设（可选）

Any hypothesis about the cause?
(Press enter to skip)

For Chore/Refactor Tracks

针对杂务/重构类Track

Q1: Task Summary

What needs to be done?
[If argument provided, confirm]

Q2: Motivation

Why is this work needed?

Q3: Success Criteria

How will we know this is complete?

Q4: Risk Assessment

What could go wrong? Any risky changes?

Q1: 任务摘要

What needs to be done?
[If argument provided, confirm]

Q2: 动机

Why is this work needed?

Q3: 成功标准

How will we know this is complete?

Q4: 风险评估

What could go wrong? Any risky changes?

Track ID Generation

Track ID生成

Generate track ID in format:

{shortname}_{YYYYMMDD}

Extract shortname from feature/bug summary (2-3 words, lowercase, hyphenated)
Use current date
Example:
```
user-auth_20250115
```
,
```
nav-bug_20250115
```

Validate uniqueness:

Check
```
conductor/tracks.md
```
for existing IDs
If collision, append counter:
```
user-auth_20250115_2
```

按照

{shortname}_{YYYYMMDD}

格式生成Track ID：

从功能/Bug摘要中提取短名称（2-3个单词，小写，连字符连接）
使用当前日期
示例：
```
user-auth_20250115
```
,
```
nav-bug_20250115
```

验证唯一性：

检查
```
conductor/tracks.md
```
中是否存在相同ID
若重复，追加计数器：
```
user-auth_20250115_2
```

Specification Generation

规格说明生成

Create

conductor/tracks/{trackId}/spec.md

markdown

undefined

创建

conductor/tracks/{trackId}/spec.md

：

markdown

undefined

Specification: {Track Title}

Track ID: {trackId} Type: {Feature|Bug|Chore|Refactor} Created: {YYYY-MM-DD} Status: Draft

Summary

{1-2 sentence summary}

Context

{Product context from product.md relevant to this track}

User Story (for features)

As a {user}, I want to {action} so that {benefit}.

Problem Description (for bugs)

{Bug description, steps to reproduce}

Acceptance Criteria

Dependencies

{List dependencies or "None"}

Out of Scope

{Explicit exclusions}

Technical Notes

{Technical considerations or "None specified"}

Generated by Conductor. Review and edit as needed.

undefined

{Technical considerations or "None specified"}

Generated by Conductor. Review and edit as needed.

undefined

User Review of Spec

用户审阅规格说明

Display the generated spec and ask:

Here is the specification I've generated:

{spec content}

Is this specification correct?
1. Yes, proceed to plan generation
2. No, let me edit (opens for inline edits)
3. Start over with different inputs

展示生成的规格说明并询问：

Here is the specification I've generated:

{spec content}

Is this specification correct?
1. Yes, proceed to plan generation
2. No, let me edit (opens for inline edits)
3. Start over with different inputs

Plan Generation

计划生成

After spec approval, generate

conductor/tracks/{trackId}/plan.md

规格说明获批后，生成

conductor/tracks/{trackId}/plan.md

：

Plan Structure

计划结构

markdown

undefined

markdown

undefined

Implementation Plan: {Track Title}

Track ID: {trackId} Spec: spec.md Created: {YYYY-MM-DD} Status: [ ] Not Started

Overview

{Brief summary of implementation approach}

Phase 1: {Phase Name}

{Phase description}

Tasks

Verification

{Verification step for phase 1}

{Verification step for phase 1}

Phase 2: {Phase Name}

{Phase description}

Tasks

Task 2.1: {Description}
Task 2.2: {Description}

Task 2.1: {Description}
Task 2.2: {Description}

Verification

{Verification step for phase 2}

{Verification step for phase 2}

Phase 3: {Phase Name} (if needed)

...

Final Verification

All acceptance criteria met
Tests passing
Documentation updated (if applicable)
Ready for review

Generated by Conductor. Tasks will be marked [~] in progress and [x] complete.

undefined

All acceptance criteria met
Tests passing
Documentation updated (if applicable)
Ready for review

Generated by Conductor. Tasks will be marked [~] in progress and [x] complete.

undefined

Phase Guidelines

阶段指导原则

Group related tasks into logical phases
Each phase should be independently verifiable
Include verification task after each phase
TDD tracks: Include test writing tasks before implementation tasks
Typical structure:
1. Setup/Foundation - Initial scaffolding, interfaces
2. Core Implementation - Main functionality
3. Integration - Connect with existing system
4. Polish - Error handling, edge cases, docs

将相关任务分组为逻辑阶段
每个阶段应可独立验证
每个阶段后包含验证任务
TDD类Track：在实现任务前包含测试编写任务
典型结构：
1. 准备/基础搭建 - 初始框架、接口
2. 核心实现 - 主要功能
3. 集成 - 与现有系统对接
4. 优化 - 错误处理、边缘情况、文档

User Review of Plan

用户审阅计划

Display the generated plan and ask:

Here is the implementation plan:

{plan content}

Is this plan correct?
1. Yes, create the track
2. No, let me edit (opens for inline edits)
3. Add more phases/tasks
4. Start over

展示生成的计划并询问：

Here is the implementation plan:

{plan content}

Is this plan correct?
1. Yes, create the track
2. No, let me edit (opens for inline edits)
3. Add more phases/tasks
4. Start over

Track Creation

Track创建

After plan approval:

Create directory structure:

conductor/tracks/{trackId}/
├── spec.md
├── plan.md
├── metadata.json
└── index.md

Create

metadata.json

json

{
  "id": "{trackId}",
  "title": "{Track Title}",
  "type": "feature|bug|chore|refactor",
  "status": "pending",
  "created": "ISO_TIMESTAMP",
  "updated": "ISO_TIMESTAMP",
  "phases": {
    "total": N,
    "completed": 0
  },
  "tasks": {
    "total": M,
    "completed": 0
  }
}

Create

index.md

markdown

# Track: {Track Title}

**ID:** {trackId}
**Status:** Pending

## Documents

- Specification
- Implementation Plan

## Progress

- Phases: 0/{N} complete
- Tasks: 0/{M} complete

## Quick Links

- Back to Tracks
- Product Context

conductor/tracks.md

Add row to tracks table

Format:

| [ ] | {trackId} | {title} | {created} | {created} |

Update
```
conductor/index.md
```
:
- Add track to "Active Tracks" section

计划获批后：

创建目录结构：

conductor/tracks/{trackId}/
├── spec.md
├── plan.md
├── metadata.json
└── index.md

创建

metadata.json

：

json

{
  "id": "{trackId}",
  "title": "{Track Title}",
  "type": "feature|bug|chore|refactor",
  "status": "pending",
  "created": "ISO_TIMESTAMP",
  "updated": "ISO_TIMESTAMP",
  "phases": {
    "total": N,
    "completed": 0
  },
  "tasks": {
    "total": M,
    "completed": 0
  }
}

创建

index.md

：

markdown

# Track: {Track Title}

**ID:** {trackId}
**Status:** Pending

## Documents

- Specification
- Implementation Plan

## Progress

- Phases: 0/{N} complete
- Tasks: 0/{M} complete

## Quick Links

- Back to Tracks
- Product Context

在

conductor/tracks.md

中注册：

向Tracks表格添加行

格式：

| [ ] | {trackId} | {title} | {created} | {created} |

更新
```
conductor/index.md
```
：
- 将Track添加到“活跃Tracks”部分

Completion Message

完成提示

Track created successfully!

Track ID: {trackId}
Location: conductor/tracks/{trackId}/

Files created:
- spec.md - Requirements specification
- plan.md - Phased implementation plan
- metadata.json - Track metadata
- index.md - Track navigation

Next steps:
1. Review spec.md and plan.md, make any edits
2. Run /conductor:implement {trackId} to start implementation
3. Run /conductor:status to see project progress

Track created successfully!

Track ID: {trackId}
Location: conductor/tracks/{trackId}/

Files created:
- spec.md - Requirements specification
- plan.md - Phased implementation plan
- metadata.json - Track metadata
- index.md - Track navigation

Next steps:
1. Review spec.md and plan.md, make any edits
2. Run /conductor:implement {trackId} to start implementation
3. Run /conductor:status to see project progress

Error Handling

错误处理

If directory creation fails: Halt and report, do not register in tracks.md
If any file write fails: Clean up partial track, report error
If tracks.md update fails: Warn user to manually register track

若目录创建失败：终止操作并报告，不要在tracks.md中注册
若任何文件写入失败：清理部分创建的Track，报告错误
若tracks.md更新失败：提醒用户手动注册Track