ln-200-scope-decomposer

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Scope Decomposer (Top Orchestrator)

范围分解器（顶层协调器）

Top-level orchestrator for complete initiative decomposition from scope to User Stories through Epic and Story coordinators.

作为顶层协调器，负责将新举措从范围通过Epic和用户故事协调器完整分解为用户故事。

Overview

概述

What This Skill Does

该技能的作用

Coordinates the complete decomposition pipeline for new initiatives:

Auto-discovers Team ID from kanban_board.md
Phase 1: Discovery (Team ID)
Phase 2: Epic Decomposition (delegates to ln-210-epic-coordinator)
Phase 3: Story Decomposition Loop (delegates to ln-220-story-coordinator per Epic, sequential)
Phase 4: Summary (total counts + next steps)

协调新举措的完整分解流程：

从kanban_board.md自动发现Team ID
阶段1：发现（Team ID）
阶段2：Epic分解（委托给ln-210-epic-coordinator）
阶段3：用户故事分解循环（按Epic依次委托给ln-220-story-coordinator）
阶段4：总结（总数量 + 后续步骤）

When to Use This Skill

何时使用该技能

This skill should be used when:

Start new initiative requiring full decomposition (scope → Epics → Stories)
Automate Epic + Story creation in single workflow
Prefer full pipeline over manual step-by-step invocation
Time-efficient approach for new projects (2-3 hours end-to-end)

Alternative: For granular control, invoke coordinators manually:

ln-210-epic-coordinator - CREATE/REPLAN Epics
ln-220-story-coordinator - CREATE/REPLAN Stories (once per Epic)

在以下场景中应使用此技能：

启动需要完整分解（范围→Epic→用户故事）的新举措
在单一工作流中自动化Epic + 用户故事的创建
偏好完整流程而非手动分步调用
新项目的高效处理方式（端到端耗时2-3小时）

替代方案： 如需精细控制，可手动调用协调器：

ln-210-epic-coordinator - CREATE/REPLAN Epics
ln-220-story-coordinator - CREATE/REPLAN Stories (once per Epic)

When NOT to Use

何时不应使用

Do NOT use if:

Initiative already has Epics → Use ln-210-epic-coordinator REPLAN mode instead
Need to replan existing Stories → Use ln-220-story-coordinator REPLAN mode per Epic
Only need Epic creation → Use ln-210-epic-coordinator directly
Only need Story creation for specific Epic → Use ln-220-story-coordinator directly

请勿在以下场景中使用：

举措已存在Epics → 改为使用ln-210-epic-coordinator REPLAN模式
需要重新规划现有Stories → 按Epic使用ln-220-story-coordinator REPLAN模式
仅需创建Epic → 直接使用ln-210-epic-coordinator
仅需为特定Epic创建Story → 直接使用ln-220-story-coordinator

Core Concepts

核心概念

Orchestrator Pattern

协调器模式

ln-200-scope-decomposer is a pure coordinator - it does NOT execute work directly:

✅ Discovers context (Team ID)
✅ Makes routing decisions (which coordinator to invoke)
✅ Delegates all work via Skill tool (ln-210, ln-220)
✅ Manages workflow state (Epic creation → Story loop)
❌ Does NOT research project docs (ln-210 does this)
❌ Does NOT generate Epic/Story documents (ln-210/ln-220 do this)
❌ Does NOT create Linear issues (coordinators do this)
❌ Does NOT prompt user (coordinators handle all user interaction)

Coordinators:

ln-210-epic-coordinator: Creates 3-7 Epics (Epic 0 for Infrastructure if applicable, Epic 1-N for business domains)
ln-220-story-coordinator: Creates 5-10 Stories per Epic (with standards research via ln-001)

ln-200-scope-decomposer是纯协调器 - 它不直接执行工作：

✅ 发现上下文（Team ID）
✅ 做出路由决策（调用哪个协调器）
✅ 通过Skill工具委托所有工作（ln-210、ln-220）
✅ 管理工作流状态（Epic创建→Story循环）
❌ 不研究项目文档（由ln-210执行）
❌ 不生成Epic/Story文档（由ln-210/ln-220执行）
❌ 不创建Linear任务（由协调器执行）
❌ 不提示用户（所有用户交互由协调器处理）

协调器：

ln-210-epic-coordinator： 创建3-7个Epics（如适用，Epic 0用于基础设施，Epic 1-N用于业务领域）
ln-220-story-coordinator： 每个Epic创建5-10个Stories（通过ln-001研究标准）

Sequential Story Decomposition

顺序Story分解

CRITICAL CONSTRAINT: Epic N Stories MUST complete before Epic N+1 starts.

Why sequential?

ln-220-story-coordinator includes user interaction (Story preview confirmation)
Interactive dialog cannot be parallelized (user must review each Epic's Stories)
Ensures Epic N Stories are approved and created before starting Epic N+1

Example: 6 Epics → ln-220 invoked 6 times sequentially (Epic 0 → Epic 1 → Epic 2 → ... → Epic 5)

关键约束： 必须完成Epic N的Stories后，才能开始Epic N+1的Story分解。

为何采用顺序方式？

ln-220-story-coordinator包含用户交互（Story预览确认）
交互式对话无法并行处理（用户必须审核每个Epic的Stories）
确保Epic N的Stories获得批准并创建后，再开始Epic N+1的工作

示例： 6个Epics → 依次调用ln-220共6次（Epic 0→Epic 1→Epic 2→…→Epic 5）

Infrastructure Epic = Epic 0

基础设施Epic = Epic 0

Reserved number: Epic 0 is reserved for Infrastructure Epic (if proposed by ln-210).

Numbering:

IF Infrastructure Epic exists → Epic 0 (Infrastructure), Epic 1-N (business domains)
ELSE → Epic 1-N (business domains only)

Decision: ln-210-epic-coordinator Phase 1 Step 3 automatically determines if Infrastructure Epic is needed (new project, multi-stack, security/monitoring requirements).

保留编号： Epic 0专为基础设施Epic保留（如由ln-210提出）。

编号规则：

若存在基础设施Epic → Epic 0（基础设施），Epic 1-N（业务领域）
若无 → Epic 1-N（仅业务领域）

决策： ln-210-epic-coordinator Phase 1 Step 3会自动判断是否需要基础设施Epic（新项目、多栈、安全/监控需求）。

Auto-Discovery

自动发现

Team ID: Auto-discovered from

docs/tasks/kanban_board.md

Linear Configuration table (see CLAUDE.md "Configuration Auto-Discovery").

Fallback: If kanban_board.md missing → ln-210-epic-coordinator will ask user directly

Team ID： 从

docs/tasks/kanban_board.md

的Linear配置表自动发现（参见CLAUDE.md中的“Configuration Auto-Discovery”）。

回退方案： 若kanban_board.md缺失 → ln-210-epic-coordinator将直接询问用户

Workflow

工作流

Phase 1: Discovery (Automated)

Auto-discovers Team ID from

docs/tasks/kanban_board.md

Validation:

Team ID exists in kanban_board.md
If missing → Skip (ln-210 will request from user)

NO user confirmation at orchestrator level - coordinators handle all user interaction.

Output: Team ID (or None if not found)

从

docs/tasks/kanban_board.md

自动发现Team ID。

验证：

Team ID存在于kanban_board.md中
若缺失 → 跳过（ln-210会向用户请求）

协调器层面无需用户确认 - 所有用户交互由协调器处理。

Output: Team ID (or None if not found)

Phase 2: Epic Decomposition (Delegated)

Objective: Create all Epics for initiative.

Delegate to ln-210-epic-coordinator:

🔄 [ORCHESTRATOR] Phase 2: Delegating Epic creation to ln-210-epic-coordinator

Skill(skill: "ln-210-epic-coordinator")

ln-210-epic-coordinator will:

Phase 1: Research project docs (requirements.md, architecture.md, tech_stack.md)
Phase 2: Auto-propose domains + Infrastructure Epic (Epic 0) → User confirms domain list
Phase 3: Build IDEAL Epic plan (Epic 0-N)
Phase 5a: Auto-extract Q1-Q4 from docs → Generate ALL Epic documents → Show batch preview → User confirms → Create all Epics
Return: Epic URLs + summary

After completion: Epics created in Linear, kanban_board.md updated.

Output: 3-7 Epics created (Epic 0 for Infrastructure if applicable, Epic 1-N for business domains)

目标： 为举措创建所有Epics。

委托给ln-210-epic-coordinator：

🔄 [ORCHESTRATOR] Phase 2: Delegating Epic creation to ln-210-epic-coordinator

Skill(skill: "ln-210-epic-coordinator")

ln-210-epic-coordinator将执行以下操作：

Phase 1: 研究项目文档（requirements.md, architecture.md, tech_stack.md）
Phase 2: 自动提议领域 + 基础设施Epic（Epic 0）→ 用户确认领域列表
Phase 3: 构建理想的Epic计划（Epic 0-N）
Phase 5a: 从文档中自动提取Q1-Q4 → 生成所有Epic文档 → 显示批量预览 → 用户确认 → 创建所有Epics
返回: Epic URLs + summary

完成后： 在Linear中创建Epics，更新kanban_board.md。

Output: 创建3-7个Epics（如适用，Epic 0用于基础设施，Epic 1-N用于业务领域）

Phase 3: Story Decomposition Loop (Sequential, Delegated)

Objective: Create Stories for EACH Epic (sequential processing).

Sequential Loop Logic:

FOR EACH Epic (Epic 0, Epic 1, ..., Epic N):
    1. Invoke ln-220-story-coordinator for current Epic
    2. Wait for completion
    3. Verify Stories created in kanban_board.md
    4. Move to next Epic

Invocation per Epic:

🔄 [ORCHESTRATOR] Phase 3: Delegating Story creation for Epic N to ln-220-story-coordinator

Skill(skill: "ln-220-story-coordinator", epic_number="Epic N")

ln-220-story-coordinator will (per Epic):

Phase 1: Auto-extract Q1-Q6 from Epic + Fallback search (requirements.md, tech_stack.md)
Phase 2: Research standards via ln-001-standards-researcher (auto)
Phase 3: Build IDEAL Story plan (5-10 Stories)
Phase 4a: Generate ALL Story documents → Show preview → User confirms → Create all Stories
Return: Story URLs + summary

Sequential constraint explanation:

ln-220 includes user interaction (Story preview confirmation)
Cannot parallelize - user must review each Epic's Stories sequentially
Epic N Stories approved → Epic N+1 Stories generated

After each Epic: Stories created in Linear, kanban_board.md updated.

Output: 30-60 Stories total (5-10 per Epic × 3-7 Epics)

TodoWrite format (mandatory): Add phases and Epic iterations to todos before starting:

- Phase 1: Discovery (in_progress)
- Phase 2: Delegate to ln-210-epic-coordinator (pending)
- Phase 3: Delegate to ln-220 for Epic 0 (pending)
- Phase 3: Delegate to ln-220 for Epic 1 (pending)
- Phase 3: Delegate to ln-220 for Epic 2 (pending)
... (one todo per Epic)
- Phase 4: Summary (pending)

Mark each as in_progress when starting, completed when coordinator returns success.

目标： 为每个Epic创建Stories（顺序处理）。

顺序循环逻辑：

FOR EACH Epic (Epic 0, Epic 1, ..., Epic N):
    1. 为当前Epic调用ln-220-story-coordinator
    2. 等待完成
    3. 验证kanban_board.md中已创建Stories
    4. 处理下一个Epic

每个Epic的调用方式：

🔄 [ORCHESTRATOR] Phase 3: Delegating Story creation for Epic N to ln-220-story-coordinator

Skill(skill: "ln-220-story-coordinator", epic_number="Epic N")

ln-220-story-coordinator将为每个Epic执行以下操作：

Phase 1: 从Epic中自动提取Q1-Q6 + 回退搜索（requirements.md, tech_stack.md）
Phase 2: 通过ln-001-standards-researcher自动研究标准
Phase 3: 构建理想的Story计划（5-10个Stories）
Phase 4a: 生成所有Story文档 → 显示预览 → 用户确认 → 创建所有Stories
返回: Story URLs + summary

顺序约束说明：

ln-220包含用户交互（Story预览确认）
无法并行处理 - 用户必须依次审核每个Epic的Stories
Epic N的Stories获得批准后 → 生成Epic N+1的Stories

每个Epic完成后： 在Linear中创建Stories，更新kanban_board.md。

Output: 共创建30-60个Stories（每个Epic 5-10个 × 3-7个Epics）

TodoWrite格式（必填）： 开始前在待办事项中添加阶段和Epic迭代：

- Phase 1: Discovery (in_progress)
- Phase 2: Delegate to ln-210-epic-coordinator (pending)
- Phase 3: Delegate to ln-220 for Epic 0 (pending)
- Phase 3: Delegate to ln-220 for Epic 1 (pending)
- Phase 3: Delegate to ln-220 for Epic 2 (pending)
... (one todo per Epic)
- Phase 4: Summary (pending)

开始时标记为in_progress，协调器返回成功后标记为completed。

Phase 4: Summary and Next Steps

Objective: Provide complete decomposition overview.

🔄 [ORCHESTRATOR] Phase 4: Full decomposition complete

Initiative Decomposition Summary:
- Epics created: N Projects (Epic 0: Infrastructure [if exists], Epic 1-N: Business domains)
- Stories created: M Issues (breakdown per Epic)
- Location: docs/tasks/kanban_board.md

Next Steps:
1. Run ln-310-story-validator to validate all Stories
2. Use ln-400-story-executor to process each Story (tasks → execution → Done)
   OR use ln-300-task-coordinator to create tasks manually for each Story

Output: Summary message with full decomposition results

目标： 提供完整的分解概述。

🔄 [ORCHESTRATOR] Phase 4: Full decomposition complete

Initiative Decomposition Summary:
- Epics created: N Projects (Epic 0: Infrastructure [if exists], Epic 1-N: Business domains)
- Stories created: M Issues (breakdown per Epic)
- Location: docs/tasks/kanban_board.md

Next Steps:
1. Run ln-310-story-validator to validate all Stories
2. Use ln-400-story-executor to process each Story (tasks → execution → Done)
   OR use ln-300-task-coordinator to create tasks manually for each Story

Output: 包含完整分解结果的总结消息

Critical Rules

关键规则

1. Pure Orchestrator Pattern

1. 纯协调器模式

Orchestrator responsibilities:

✅ Discovery (Team ID)
✅ Routing decisions (which coordinator to invoke, when)
✅ Sequential loop management (Epic 0 → Epic 1 → ... → Epic N)
✅ Summary aggregation (count Epics, Stories)

Coordinator responsibilities (NOT orchestrator):

❌ Research project docs → ln-210
❌ Auto-extract Epic/Story info → ln-210/ln-220
❌ Generate Epic/Story documents → ln-210/ln-220
❌ Create Linear issues → ln-210/ln-220
❌ User interaction (confirmations) → ln-210/ln-220

协调器职责：

✅ 发现（Team ID）
✅ 路由决策（调用哪个协调器、何时调用）
✅ 顺序循环管理（Epic 0→Epic 1→…→Epic N）
✅ 总结聚合（统计Epic、Story数量）

协调器职责（非协调器的工作）：

❌ 研究项目文档 → ln-210
❌ 自动提取Epic/Story信息 → ln-210/ln-220
❌ 生成Epic/Story文档 → ln-210/ln-220
❌ 创建Linear任务 → ln-210/ln-220
❌ 用户交互（确认） → ln-210/ln-220

2. Sequential Story Decomposition

2. 顺序Story分解

HARD RULE: Epic N Stories MUST complete before Epic N+1 starts.

Rationale: ln-220 includes user interaction (Story preview confirmation). Interactive dialog cannot be parallelized.

Example: 6 Epics → 6 sequential ln-220 invocations (Epic 0 → Epic 1 → ... → Epic 5)

硬性规则： 必须完成Epic N的Stories后，才能开始Epic N+1的Stories。

理由： ln-220包含用户交互（Story预览确认）。交互式对话无法并行处理。

示例： 6个Epics → 依次调用ln-220共6次（Epic 0→Epic 1→…→Epic 5）

3. No User Prompts at Orchestrator Level

3. 协调器层面不提示用户

Orchestrator does NOT prompt user:

❌ NO "Proceed with decomposition?" confirmation (redundant - coordinators already confirm)
❌ NO time estimates (misleading - actual time varies)
❌ NO Epic/Story previews (coordinators handle this)

All user interaction delegated to coordinators:

ln-210 Phase 2: Domain approval (USER CONTROL POINT 1)
ln-210 Phase 5a: Epic batch preview (USER CONTROL POINT 2)
ln-220 Phase 4a: Story preview per Epic (USER CONTROL POINT 3, N times)

协调器不提示用户：

❌ 不询问“是否继续分解？”（冗余 - 协调器已进行确认）
❌ 不提供时间估算（易误导 - 实际时间各不相同）
❌ 不提供Epic/Story预览（由协调器处理）

所有用户交互委托给协调器：

ln-210 Phase 2: 领域批准（USER CONTROL POINT 1）
ln-210 Phase 5a: Epic批量预览（USER CONTROL POINT 2）
ln-220 Phase 4a: 每个Epic的Story预览（USER CONTROL POINT 3，共N次）

4. Epic 0 for Infrastructure

4. Epic 0用于基础设施

Reserved number: Epic 0 is reserved for Infrastructure Epic.

Decision point: ln-210-epic-coordinator Phase 1 Step 3 automatically determines if Infrastructure Epic needed.

Numbering: Epic 0 (if Infrastructure), Epic 1-N (business domains)

保留编号： Epic 0专为基础设施Epic保留。

决策点： ln-210-epic-coordinator Phase 1 Step 3会自动判断是否需要基础设施Epic。

编号规则： Epic 0（若有基础设施），Epic 1-N（业务领域）

Definition of Done

完成定义

Integration with Ecosystem

与生态系统的集成

Called By

Users directly: "Decompose initiative: [initiative name]" or "Create epics and stories for [project]"

用户直接调用："Decompose initiative: [initiative name]" 或 "Create epics and stories for [project]"

Calls (via Skill tool)

ln-210-epic-coordinator (Phase 2) - CREATE mode (batch Epic creation with batch preview)
ln-220-story-coordinator (Phase 3, sequential loop) - CREATE mode per Epic (Story creation with preview)

ln-210-epic-coordinator (Phase 2) - CREATE模式（批量创建Epic并提供批量预览）
ln-220-story-coordinator (Phase 3, sequential loop) - 每个Epic使用CREATE模式（创建Story并提供预览）

Downstream

After ln-200-scope-decomposer completes:

ln-310-story-validator - validates all created Stories before task creation
ln-400-story-executor - processes each Story (tasks → execution → Done)
- OR ln-300-task-coordinator - creates tasks manually for each Story

ln-200-scope-decomposer完成后：

ln-310-story-validator - 在创建任务前验证所有已创建的Stories
ln-400-story-executor - 处理每个Story（tasks → execution → Done）
- 或 ln-300-task-coordinator - 为每个Story手动创建任务

Best Practices

最佳实践

Orchestrator Responsibilities

协调器职责

DO:

✅ Auto-discover Team ID
✅ Delegate to coordinators
✅ Manage sequential loop (Epic 0 → Epic 1 → ... → Epic N)
✅ Aggregate summary (count Epics, Stories)

DON'T:

❌ Research project docs (ln-210 does this)
❌ Generate documents (coordinators do this)
❌ Create Linear issues (coordinators do this)
❌ Prompt user (coordinators handle all interaction)

应做：

✅ 自动发现Team ID
✅ 委托给协调器
✅ 管理顺序循环（Epic 0→Epic 1→…→Epic N）
✅ 聚合总结（统计Epic、Story数量）

不应做：

❌ 研究项目文档（由ln-210执行）
❌ 生成文档（由协调器执行）
❌ 创建Linear任务（由协调器执行）
❌ 提示用户（所有交互由协调器处理）

Coordinator Trust

信任协调器结果

Trust coordinator results: Coordinators return summary, orchestrator doesn't re-verify.

Error handling: If coordinator returns error, report to user and stop pipeline.

信任协调器结果： 协调器返回summary，协调器不重新验证。

错误处理： 若协调器返回错误，向用户报告并停止流程。

Sequential Processing

顺序处理

Epic creation first: Phase 2 creates ALL Epics before Phase 3 starts (ensures Epic IDs available).

Story creation sequential: Phase 3 processes Epics one-by-one (Epic N Stories → Epic N+1 Stories).

Rationale: User interaction in ln-220 requires sequential processing (cannot parallelize confirmations).

先创建Epic： Phase 2先创建所有Epics，再开始Phase 3（确保Epic IDs可用）。

顺序创建Story： Phase 3逐个处理Epics（Epic N的Stories→Epic N+1的Stories）。

理由： ln-220中的用户交互需要顺序处理（无法并行确认）。

Time Estimates

时间估算

Realistic estimate: 2-3 hours for full decomposition (6 Epics × 7 Stories avg = 42 Stories).

Breakdown:

Phase 2 (Epic creation): 30-45 min (batch preview reduces time)
Phase 3 (Story creation): 1.5-2 hours (6 Epics × 15-20 min per Epic)
Phase 4 (Summary): 2 min

Do NOT provide time estimates to user - varies based on project complexity and user response time.

实际估算： 完整分解耗时2-3小时（平均6个Epics×7个Stories=42个Stories）。

细分：

Phase 2（Epic创建）：30-45分钟（批量预览减少时间）
Phase 3（Story创建）：1.5-2小时（6个Epics×每个Epic15-20分钟）
Phase 4（总结）：2分钟

请勿向用户提供时间估算 - 因项目复杂度和用户响应时间而异。

Example Usage

使用示例

Request:

"Decompose initiative: E-commerce Platform"

Execution:

Phase 1: Discovery
- Team ID loaded from kanban_board.md
Phase 2: Epic Decomposition
- Invoke ln-210-epic-coordinator
- ln-210 creates 6 Epics:
  - Epic 11 (Infrastructure Epic 0 pattern)
  - Epic 12-16 (business domains)
- Output: 6 Epic URLs
Phase 3: Story Decomposition Loop (Sequential)
- Epic 11: Invoke ln-220 → 6 Stories (US017-US022)
- Epic 12: Invoke ln-220 → 7 Stories (US023-US029)
- Epic 13: Invoke ln-220 → 5 Stories (US030-US034)
- Epic 14: Invoke ln-220 → 6 Stories (US035-US040)
- Epic 15: Invoke ln-220 → 7 Stories (US041-US047)
- Epic 16: Invoke ln-220 → 5 Stories (US048-US052)
- Output: 36 Stories total

Phase 4: Summary

🔄 [ORCHESTRATOR] Full decomposition complete

Initiative: E-commerce Platform
- Epics created: 6 Projects (Epic 11: Infrastructure, Epic 12-16: Business domains)
- Stories created: 36 Issues
  - Epic 11: 6 Stories
  - Epic 12: 7 Stories
  - Epic 13: 5 Stories
  - Epic 14: 6 Stories
  - Epic 15: 7 Stories
  - Epic 16: 5 Stories
- Location: docs/tasks/kanban_board.md

Next Steps:
1. Run ln-310-story-validator to validate all Stories
2. Use ln-400-story-executor to process each Story (tasks → execution → Done)

Result: 6 Epics + 36 Stories created through full pipeline automation

请求：

"Decompose initiative: E-commerce Platform"

执行：

Phase 1: Discovery
- 从kanban_board.md加载Team ID
Phase 2: Epic Decomposition
- 调用ln-210-epic-coordinator
- ln-210创建6个Epics:
  - Epic 11（基础设施Epic 0模式）
  - Epic 12-16（业务领域）
- Output: 6个Epic URLs
Phase 3: Story Decomposition Loop (Sequential)
- Epic 11: 调用ln-220 → 6个Stories (US017-US022)
- Epic 12: 调用ln-220 → 7个Stories (US023-US029)
- Epic 13: 调用ln-220 → 5个Stories (US030-US034)
- Epic 14: 调用ln-220 → 6个Stories (US035-US040)
- Epic 15: 调用ln-220 → 7个Stories (US041-US047)
- Epic 16: 调用ln-220 → 5个Stories (US048-US052)
- Output: 共36个Stories

Phase 4: Summary

🔄 [ORCHESTRATOR] Full decomposition complete

Initiative: E-commerce Platform
- Epics created: 6 Projects (Epic 11: Infrastructure, Epic 12-16: Business domains)
- Stories created: 36 Issues
  - Epic 11: 6 Stories
  - Epic 12: 7 Stories
  - Epic 13: 5 Stories
  - Epic 14: 6 Stories
  - Epic 15: 7 Stories
  - Epic 16: 5 Stories
- Location: docs/tasks/kanban_board.md

Next Steps:
1. Run ln-310-story-validator to validate all Stories
2. Use ln-400-story-executor to process each Story (tasks → execution → Done)

结果： 通过完整流程自动化创建了6个Epics + 36个Stories

Chat Output Prefix

Use emoji prefix for visual differentiation:

🔄 [ORCHESTRATOR] - ln-200-scope-decomposer (top orchestrator)

Purpose: Helps users track orchestrator progress when delegating to multiple coordinators.

Version: 2.0.0 (BREAKING: Complete rewrite following ln-400 Pure Orchestrator Pattern. Removed Phase 1 User Confirmation. Removed false "AUTOMATIC" claims. Added Epic 0 for Infrastructure. Added Sequential Story Decomposition explanation. Added Critical Rules section. Realistic time estimates (2-3h). Removed REPLAN mode (not applicable to top orchestrator - use ln-210/ln-220 REPLAN modes instead).) Last Updated: 2025-11-20

使用表情前缀进行视觉区分：

🔄 [ORCHESTRATOR] - ln-200-scope-decomposer（顶层协调器）

目的： 当委托给多个协调器时，帮助用户跟踪协调器的进度。

Version: 2.0.0 (BREAKING: 遵循ln-400 Pure Orchestrator Pattern完全重写。移除Phase 1 User Confirmation。移除错误的"AUTOMATIC"声明。添加Epic 0用于基础设施。添加Sequential Story Decomposition说明。添加Critical Rules section。实际时间估算(2-3h)。移除REPLAN模式（不适用于顶层协调器 - 改用ln-210/ln-220的REPLAN模式）。) Last Updated: 2025-11-20