ln-300-task-coordinator by levnikolaevich/claude-code-skills
npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-300-task-coordinator路径说明: 文件路径(
shared/、references/、../ln-*)是相对于技能仓库根目录的。如果在当前工作目录未找到,请定位此 SKILL.md 文件所在的目录并向上返回一级以找到仓库根目录。如果缺少shared/目录,请通过 WebFetch 从https://raw.githubusercontent.com/levnikolaevich/claude-code-skills/master/skills/{path}获取文件。
协调为故事创建或重新规划实施任务。首先构建理想计划,然后分派给执行者。
| 输入 | 必需 | 来源 | 描述 |
|---|---|---|---|
storyId |
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
| 是 |
| args, git branch, kanban, user |
| 要处理的故事 |
解析方式: 故事解析链。状态过滤器: Backlog, Todo
必须阅读: 加载 shared/references/tools_config_guide.md、shared/references/storage_mode_detection.md 和 shared/references/input_resolution_pattern.md
提取:task_provider = 任务管理 → 提供者 (linear | file)。
执行者(ln-301, ln-302)根据 task_provider 处理实际的 Linear/文件操作。
必须阅读: 加载 shared/references/creation_quality_checklist.md §任务创建检查清单,了解 ln-310 将强制执行验证标准。
shared/references/goal_articulation_gate.md — 在构建理想计划之前,用一句话陈述此故事的真实目标(交付成果,而非过程)。验证:分解是否服务于此目标?然后:加载故事(验收标准、技术说明、上下文),评估复杂性,构建理想计划(仅限 1-8 个实施任务),扫描可重用模式(在 src/ 中搜索与任务类别相关的错误处理程序、验证器、实用工具 — 仅计数;如果找到,在相关任务描述中追加 **模式提示:** 在 src/ 目录中有 {count} 个现有的 {category} 模式。在创建新内容之前,请先审查以重用(ln-401 中的步骤 4a)。),应用基础优先的执行顺序,验证任务独立性,分配并行组,为每个任务验收标准定义验证方法,提取指南链接。.tsx/.vue/.svelte/.html/.css 文件 → 插入“设计定义”作为任务 1(并行组 1):验收标准:(1) 陈述视觉主题(1 句话:情绪、材质、能量),(2) 定义内容计划(章节顺序),(3) 定义交互计划(2-3 个有目的的动作),(4) 如果项目有 design_guidelines.md → 加载并交叉引用。验证:检查(设计定义记录在任务评论中)。必须阅读: shared/references/frontend_design_guide.md §设计定义。上下文: 在委托给执行者之前验证计划质量,防止返工。
构建理想计划(阶段 2)后,对 7 项标准进行评分:
---|---|---
1 | 独立性 | 任务之间没有前向依赖(任务 N 仅使用 1..N-1)
2 | 验收标准清晰度 | 每个任务验收标准都有可衡量的结果和验证方法(测试/命令/检查)
3 | 技术信心 | 所有引用的技术/模式都是已知的或已研究过的
4 | 范围隔离 | 任务不与兄弟故事的任务重叠。加载兄弟故事(list_issues project=Epic.id),比较受影响组件和文件路径是否存在结构重叠
5 | 架构合规性 | 任务引用正确的层级(DB→Repo→Service→API),没有计划中的跨层违规(例如,API 任务直接进行数据库调用)
6 | 并行组有效性 | 同一组中的任务没有相互依赖;所有依赖都指向更早的组;编号是连续的
7 | 破坏性操作安全性 | 涉及数据删除/迁移/模式变更的任务包含安全计划(备份、回滚、影响范围)
分数 = 通过标准的数量 (0-7)
上下文: 目标驱动执行模式 — 在规划时定义如何验证每个验收标准,以便执行者(ln-401)在实施后可以循环进行验证。
构建理想计划(阶段 2)时,每个任务验收标准必须包含一个 verify: 方法:
| 方法 | 使用时机 | 示例 |
|---|---|---|
| test | 现有测试覆盖验收标准 | verify: test (test_auth.py::test_login_success) |
| command | CLI 命令验证结果 | verify: command (curl -X POST /users → 201) |
| inspect | 文件/输出检查 | verify: inspect (migration file has email column) |
规则: 每个任务至少有一个验收标准必须使用 test 或 command(不能全是 inspect)。
必须阅读: 加载 shared/references/ac_validation_rules.md §5 查看完整格式和示例。
根据 creation_quality_checklist.md #19(依赖关系)和 #13(基础优先顺序)的规则。
示例:
如果检测到前向依赖: 重新排序,重构以消除依赖,或拆分为顺序部分。
构建理想计划并验证独立性后,分配并行组编号,以便在 ln-400 中实现并发执行。
算法:
group = 1
FOR EACH task T IN ordered_plan:
deps = tasks that T depends on (from Related/Context)
IF any dep is in CURRENT group:
group++
T.parallel_group = group
示例:
| 任务 | 依赖关系 | 组 |
|---|---|---|
| T1: 数据库迁移 | 无 | 1 |
| T2: UserRepo | T1 | 2 |
| T3: ProductRepo | T1 | 2 |
| T4: UserService | T2 | 3 |
| T5: API 端点 | T4 | 4 |
规则:
**Parallel Group:** {N}(根据 shared/templates/task_template_implementation.md)**Parallel Group:** 字段,ln-400 将其视为自己的组(顺序执行)| 条件 | 模式 | 委托给 | 负载 |
|---|---|---|---|
| 计数 = 0 | CREATE | ln-301-task-creator | taskType=implementation, Story data, IDEAL plan, guideLinks |
| 计数 > 0 且 "add"/"append" | ADD | ln-301-task-creator | taskType=implementation, appendMode=true, newTaskDescription, guideLinks |
| 计数 > 0 且 replan 关键词 | REPLAN | ln-302-task-replanner | taskType=implementation, Story data, IDEAL plan, guideLinks, existingTaskIds |
| 计数 > 0 且不明确 | ASK | 向用户澄清 | — |
必须步骤: 必须调用执行者。切勿直接创建/更新 Linear 或任务文件。
CREATE/ADD 模式:
Skill(skill: "ln-301-task-creator", args: "{storyId}")
REPLAN 模式:
Skill(skill: "ln-302-task-replanner", args: "{storyId}")
在计划模式(只读)下调用时:
TodoWrite 格式(强制): 在开始前将阶段添加到待办事项:
- Phase 1: Discovery (in_progress)
- Phase 2: Decompose & Build IDEAL Plan (pending)
- Phase 3: Check Existing & Detect Mode (pending)
- Phase 4: Delegate to ln-301/ln-302 (pending)
- Phase 5: Verify worker result (pending)
每个阶段开始时标记为 in_progress,完成时标记为 completed。
| 模式 | 执行者 | 上下文 |
|---|---|---|
| CREATE/ADD | ln-301-task-creator | 共享(技能工具)— 根据理想计划创建任务 |
| REPLAN | ln-302-task-replanner | 共享(技能工具)— 比较理想计划与现有计划,应用更改 |
所有执行者: 在同一上下文中通过技能工具调用 — 执行者可以看到协调者的理想计划和扫描结果。
反模式:
creation_quality_checklist.md #13 的基础优先执行顺序。必须阅读: 加载 shared/references/meta_analysis_protocol.md
技能类型:planning-coordinator。在所有阶段完成后运行。使用 planning-coordinator 格式将输出发送到聊天。
shared/references/tools_config_guide.mdshared/references/storage_mode_detection.mdshared/references/problem_solving.mdshared/references/orchestrator_pattern.mdshared/references/auto_discovery_pattern.mdshared/references/decompose_first_pattern.mdshared/references/plan_mode_pattern.mdshared/references/numbering_conventions.md(每个故事的任务编号)shared/templates/task_template_implementation.mddocs/templates/task_template_implementation.md(在目标项目中,由执行者创建)ln-302-task-replanner/references/replan_algorithm.mdCLAUDE.md、docs/tasks/kanban_board.md版本: 4.0.0 最后更新: 2026-02-03
每周安装次数
148
仓库
GitHub 星标数
245
首次出现
2026年1月24日
安全审计
安装于
claude-code135
gemini-cli133
codex133
opencode133
cursor131
github-copilot128
Paths: File paths (
shared/,references/,../ln-*) are relative to skills repo root. If not found at CWD, locate this SKILL.md directory and go up one level for repo root. Ifshared/is missing, fetch files via WebFetch fromhttps://raw.githubusercontent.com/levnikolaevich/claude-code-skills/master/skills/{path}.
Coordinates creation or replanning of implementation tasks for a Story. Builds the ideal plan first, then routes to workers.
| Input | Required | Source | Description |
|---|---|---|---|
storyId | Yes | args, git branch, kanban, user | Story to process |
Resolution: Story Resolution Chain. Status filter: Backlog, Todo
MANDATORY READ: Load shared/references/tools_config_guide.md, shared/references/storage_mode_detection.md, and shared/references/input_resolution_pattern.md
Extract: task_provider = Task Management → Provider (linear | file).
Workers (ln-301, ln-302) handle the actual Linear/File operations based on task_provider.
MANDATORY READ: Load shared/references/creation_quality_checklist.md §Task Creation Checklist for validation criteria that ln-310 will enforce.
shared/references/goal_articulation_gate.md — Before building IDEAL plan, state REAL GOAL of this Story in one sentence (the deliverable, not the process). Verify: does the decomposition serve THIS goal? Then: Load Story (AC, Technical Notes, Context), assess complexity, build IDEAL plan (1-8 implementation tasks only), scan for reusable patterns (Grep src/ for error handlers, validators, utilities relevant to task categories — count only; if found, append **Pattern Hint:** {count} existing {category} patterns in src/. Review for reuse before creating new (Step 4a in ln-401). to relevant task descriptions), apply Foundation-First execution order, validate Task Independence , assign Parallel Groups , define verification methods for each task AC , extract guide links..tsx/.vue/.svelte/.html/.css files → insert "Design Definition" as Task 1 (Parallel Group 1): AC: (1) Visual thesis stated (1 sentence: mood, material, energy), (2) Content plan defined (section sequence), (3) Interaction plan defined (2-3 purposeful motions), (4) If project has design_guidelines.md → loaded and cross-referenced. . §Design Definition.Context: Validates plan quality before delegation to workers, preventing rework.
After building IDEAL plan (Phase 2), score 7 criteria:
---|---|---
1 | Independence | No forward dependencies between tasks (Task N uses only 1..N-1)
2 | AC clarity | Each task AC has measurable outcome AND verification method (test/command/inspect)
3 | Tech confidence | All referenced technologies/patterns are known or researched
4 | Scope isolation | Tasks don't overlap with sibling Stories' tasks. Load siblings (list_issues project=Epic.id), compare Affected Components and file paths for structural overlap
5 | Architecture compliance | Tasks reference correct layers (DB→Repo→Service→API), no planned cross-layer violations (e.g., API task doing direct DB calls)
6 | Parallel groups valid | Tasks in same group have no mutual dependencies; all deps point to earlier groups; numbers sequential
7 | Destructive op safety | Tasks with data deletion/migration/schema changes include safety plan (backup, rollback, blast radius)
Score = count of PASS criteria (0-7)
Context: Goal-Driven Execution pattern — define HOW to verify each AC at planning time so executor (ln-401) can loop through verifications after implementation.
When building IDEAL plan (Phase 2), each task AC must include a verify: method:
| Method | When to Use | Example |
|---|---|---|
| test | Existing test covers AC | verify: test (test_auth.py::test_login_success) |
| command | CLI command validates outcome | verify: command (curl -X POST /users → 201) |
| inspect | File/output check | verify: inspect (migration file has email column) |
Rule: At least 1 AC per task must use test or command (not all inspect).
MANDATORY READ: Load shared/references/ac_validation_rules.md §5 for full format and examples.
Rules per creation_quality_checklist.md #19 (dependencies) and #13 (Foundation-First order).
Examples:
If forward dependency detected: Reorder, refactor to remove dependency, or split into sequential parts.
After building IDEAL plan and validating independence, assign Parallel Group numbers to enable concurrent execution in ln-400.
Algorithm:
group = 1
FOR EACH task T IN ordered_plan:
deps = tasks that T depends on (from Related/Context)
IF any dep is in CURRENT group:
group++
T.parallel_group = group
Example:
| Task | Dependencies | Group |
|---|---|---|
| T1: DB migration | none | 1 |
| T2: UserRepo | T1 | 2 |
| T3: ProductRepo | T1 | 2 |
| T4: UserService | T2 | 3 |
| T5: API endpoint | T4 | 4 |
Rules:
**Parallel Group:** {N} in each task document (per shared/templates/task_template_implementation.md)**Parallel Group:** field, ln-400 treats it as its own group (sequential)| Condition | Mode | Delegate | Payload |
|---|---|---|---|
| Count = 0 | CREATE | ln-301-task-creator | taskType=implementation, Story data, IDEAL plan, guideLinks |
| Count > 0 AND "add"/"append" | ADD | ln-301-task-creator | taskType=implementation, appendMode=true, newTaskDescription, guideLinks |
| Count > 0 AND replan keywords | REPLAN | ln-302-task-replanner | taskType=implementation, Story data, IDEAL plan, guideLinks, existingTaskIds |
| Count > 0 AND ambiguous | ASK | Clarify with user | — |
MANDATORY STEP: Worker invocation required. Never create/update Linear or task files directly.
CREATE/ADD mode:
Skill(skill: "ln-301-task-creator", args: "{storyId}")
REPLAN mode:
Skill(skill: "ln-302-task-replanner", args: "{storyId}")
When invoked in Plan Mode (read-only):
TodoWrite format (mandatory): Add phases to todos before starting:
- Phase 1: Discovery (in_progress)
- Phase 2: Decompose & Build IDEAL Plan (pending)
- Phase 3: Check Existing & Detect Mode (pending)
- Phase 4: Delegate to ln-301/ln-302 (pending)
- Phase 5: Verify worker result (pending)
Mark each as in_progress when starting, completed when done.
| Mode | Worker | Context |
|---|---|---|
| CREATE/ADD | ln-301-task-creator | Shared (Skill tool) — creates tasks from IDEAL plan |
| REPLAN | ln-302-task-replanner | Shared (Skill tool) — compares IDEAL vs existing, applies changes |
All workers: Invoke via Skill tool in same context — workers see coordinator's IDEAL plan and scan results.
Anti-Patterns:
creation_quality_checklist.md #13.MANDATORY READ: Load shared/references/meta_analysis_protocol.md
Skill type: planning-coordinator. Run after all phases complete. Output to chat using the planning-coordinator format.
shared/references/tools_config_guide.mdshared/references/storage_mode_detection.mdshared/references/problem_solving.mdshared/references/orchestrator_pattern.mdshared/references/auto_discovery_pattern.mdshared/references/decompose_first_pattern.mdshared/references/plan_mode_pattern.mdVersion: 4.0.0 Last Updated: 2026-02-03
Weekly Installs
148
Repository
GitHub Stars
245
First Seen
Jan 24, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykWarn
Installed on
claude-code135
gemini-cli133
codex133
opencode133
cursor131
github-copilot128
通过 LiteLLM 代理让 Claude Code 对接 GitHub Copilot 运行 | 高级变通方案指南
36,300 周安装
verify: inspect (Design Definition documented in task comment)shared/references/frontend_design_guide.mdshared/references/numbering_conventions.md (Task per-Story numbering)shared/templates/task_template_implementation.mddocs/templates/task_template_implementation.md (in target project, created by workers)ln-302-task-replanner/references/replan_algorithm.mdCLAUDE.md, docs/tasks/kanban_board.md