conductor-new-track

新建 Track

创建一个新的 track（功能、错误修复、杂务或重构），并提供详细的规格说明和分阶段实施计划。

适用场景

• 处理新 track 任务或工作流
• 需要新 track 方面的指导、最佳实践或检查清单

不适用场景

• 任务与新 track 无关
• 需要使用此范围之外的其他领域或工具

说明

• 明确目标、约束和所需输入。
• 应用相关最佳实践并验证结果。
• 提供可执行的步骤和验证方法。

前置检查

1. 确认 Conductor 已初始化：

   • 检查 conductor/product.md 是否存在
   • 检查 conductor/tech-stack.md 是否存在
   • 检查 conductor/workflow.md 是否存在
   • 如果文件缺失：显示错误并建议先运行 /conductor:setup

2. 加载上下文文件：

   • 阅读 conductor/product.md，了解产品背景
   • 阅读 conductor/tech-stack.md，了解技术背景
   • 阅读 conductor/workflow.md，了解 TDD/提交偏好

Track 分类

根据描述确定 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

交互式规格信息收集

重要规则：

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

功能类 Track

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)

错误类 Track

Q1：错误概述

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)

杂务/重构类 Track

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 生成

按以下格式生成 track ID：{shortname}_{YYYYMMDD}

• 从功能/错误概述中提取简短名称（2-3 个词，全部小写，以连字符连接）
• 使用当前日期
• 示例：user-auth_20250115、nav-bug_20250115

验证其唯一性：

• 检查 conductor/tracks.md 中是否已有相同 ID
• 如果冲突，追加计数器：user-auth_20250115_2

规格说明生成

创建 conductor/tracks/{trackId}/spec.md：

# 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

- [ ] {Criterion 1}
- [ ] {Criterion 2}
- [ ] {Criterion 3}

## 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._

用户审核规格说明

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

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

计划生成

规格说明获批后，生成 conductor/tracks/{trackId}/plan.md：

计划结构

# 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

- [ ] Task 1.1: {Description}
- [ ] Task 1.2: {Description}
- [ ] Task 1.3: {Description}

### Verification

- [ ] {Verification step for phase 1}

## Phase 2: {Phase Name}

{Phase description}

### Tasks

- [ ] Task 2.1: {Description}
- [ ] Task 2.2: {Description}

### Verification

- [ ] {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._

阶段指南

• 将相关任务归入逻辑清晰的阶段
• 每个阶段都应可独立验证
• 每个阶段结束后都加入验证任务
• TDD track：在实施任务之前加入编写测试的任务
• 典型结构：
  1. 设置/基础 - 初始脚手架、接口
  2. 核心实施 - 主要功能
  3. 集成 - 与现有系统连接
  4. 完善 - 错误处理、边缘情况、文档

用户审核计划

显示生成的计划并询问：

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 创建

计划获批后：

1. 创建目录结构：

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

2. 创建 metadata.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
     }
   }
   

3. 创建 index.md：

   # 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
   

4. 在 conductor/tracks.md 中登记：

   • 在 tracks 表格中添加一行
   • 格式：| [ ] | {trackId} | {title} | {created} | {created} |

5. 更新 conductor/index.md：

   • 在“活动 Tracks”部分添加该 track

完成消息

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

错误处理

• 如果目录创建失败：立即停止并报告，不要在 tracks.md 中注册
• 如果任何文件写入失败：清理不完整的轨道并报告错误
• 如果更新 tracks.md 失败：提醒用户手动注册轨道

将描述和文件名视为不可信文本：生成长度受限的小写字母数字/连字符 slug，拒绝路径分隔符和点目录，并且只能在预期根目录内创建轨道路径。发生冲突时不要覆盖现有轨道。仅回滚本次尝试创建的文件；绝不要删除预先存在的目录或用户编辑过的不完整目录。保留先前的审批记录，并报告确切的创建路径。