Back to Details

ai-agent-implementation

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

AI Agent Implementation Skill

AI Agent 功能实现技能

Answers the question: How do I execute this feature with AI agents? What's done? What's next? What's blocking?
This skill manages the practical execution of feature tasks by AI agents, handling task batching, progress tracking, and blocker identification without calendar overhead.
解决以下问题：如何通过AI Agent执行该功能？已完成哪些工作？下一步是什么？存在哪些阻塞问题？
本技能负责通过AI Agent实际执行功能任务，处理任务分批、进度跟踪和阻塞问题识别，无需借助日历工具。

When to Use

适用场景

Use this skill when you:
  • Have an execution sequence (from feature-planning skill)
  • Are using AI agents to build features
  • Need to track which tasks are done vs. in progress
  • Have blockers to identify and manage
  • Need to coordinate work between batches
Key indicator: You're asking "What should the agent build next?" or "What's the status of this feature?"
Do NOT use this skill if:
  • You don't have an execution sequence yet (use feature-planning first)
  • You're not using AI agents (this is agent-specific)
在以下场景使用本技能：
  • 你已有执行序列（来自feature-planning技能）
  • 正在使用AI Agent构建功能
  • 需要跟踪任务的完成/进行中状态
  • 需要识别并管理阻塞问题
  • 需要协调不同批次之间的工作
关键标志：你在问“Agent接下来应该构建什么？”或“该功能的当前状态是什么？”
请勿使用本技能的情况：
  • 你还没有执行序列（请先使用feature-planning技能）
  • 你没有使用AI Agent（本技能专为Agent设计）

Prerequisites

前置条件

⚠️ CRITICAL: This skill requires an execution sequence as input.
Before using this skill:
  1. Verify you have an execution sequence first
    • If you don't have 
      docs/features/[feature-name]/implementation-sequence.md
      → Use 
      feature-planning
      first
    • If you have the sequence → Continue below
  2. Expected inputs from feature-planning:
    • docs/features/[feature-name]/implementation-sequence.md
      file exists
    • Contains complete task list with dependencies
    • Batch groupings identified
    • Critical path marked
If you don't have an execution sequence:
  • Load the 
    feature-planning
    skill first
  • Follow its workflow to sequence your tasks
  • Once you have the sequence file, return here
⚠️ 重要提示：本技能需要以执行序列作为输入。
使用本技能前：
  1. 确认你已拥有执行序列
    • 如果你没有
      docs/features/[feature-name]/implementation-sequence.md
      文件 → 请先使用
      feature-planning
      技能
    • 如果你已有该序列 → 继续下一步
  2. 来自feature-planning的预期输入：
    • 存在
      docs/features/[feature-name]/implementation-sequence.md
      文件
    • 文件包含带依赖关系的完整任务列表
    • 已划分好任务批次
    • 已标记关键路径
如果你没有执行序列：
  • 先加载
    feature-planning
    技能
  • 按照其工作流程编排任务序列
  • 获得序列文件后，再返回使用本技能

Inputs

输入项

  • Execution sequence document (required): 
    docs/features/[feature-name]/implementation-sequence.md
  • Agent session logs (optional): What agents have completed so far
  • 执行序列文档（必填）：
    docs/features/[feature-name]/implementation-sequence.md
  • Agent会话日志（可选）：记录Agent已完成的工作内容

Outputs

输出项

MANDATORY FILE ORGANIZATION: All feature files must be in 
docs/features/<feature-name>/
subdirectory.
When this skill is used during execution, it creates/updates:
  1. Execution Progress (
    docs/features/[feature-name]/implementation-progress.md
    )
    • Current status of all tasks
    • What's been completed
    • What's in progress
    • What's ready to start next
    • Any blockers or issues
    • Example: 
      docs/features/user-authentication/implementation-progress.md
  2. Blocker Log (
    docs/features/[feature-name]/blockers.md
    )
    • Current blockers preventing progress
    • Root cause analysis
    • Resolution status
    • Example: 
      docs/features/user-authentication/blockers.md
  3. Session Summary (
    docs/features/[feature-name]/session-summary-[batch-num].md
    )
    • What this agent batch completed
    • Test results and verification status
    • What to hand off to next agent/batch
    • Any issues discovered
    • Example: 
      docs/features/user-authentication/session-summary-1.md
强制文件组织规则：所有功能文件必须放在
docs/features/<feature-name>/
子目录下。
使用本技能执行任务时，会创建/更新以下内容：
  1. 执行进度文档 (
    docs/features/[feature-name]/implementation-progress.md
    )
    • 所有任务的当前状态
    • 已完成的工作
    • 进行中的工作
    • 即将启动的工作
    • 所有阻塞问题或异常
    • 示例：
      docs/features/user-authentication/implementation-progress.md
  2. 阻塞问题日志 (
    docs/features/[feature-name]/blockers.md
    )
    • 当前阻碍进度的阻塞问题
    • 根本原因分析
    • 解决状态
    • 示例：
      docs/features/user-authentication/blockers.md
  3. 会话总结文档 (
    docs/features/[feature-name]/session-summary-[batch-num].md
    )
    • 该Agent批次完成的工作
    • 测试结果和验证状态
    • 需要交接给下一个Agent/批次的内容
    • 发现的所有问题
    • 示例：
      docs/features/user-authentication/session-summary-1.md

Workflow Overview

工作流程概述

The AI agent execution process:
Execution Sequence Input
    ↓
Agent Session 1: Execute Batch 1
    ↓
Track Completion & Verify
    ↓
Identify Blockers
    ↓
Next Agent Session: Execute Batch 2
    ↓
Repeat until all tasks complete
    ↓
Feature Complete
AI Agent执行流程：
执行序列输入
    ↓
Agent会话1：执行批次1
    ↓
跟踪完成情况并验证
    ↓
识别阻塞问题
    ↓
下一个Agent会话：执行批次2
    ↓
重复直至所有任务完成
    ↓
功能构建完成

Core Workflow

核心工作流程

Phase 1: Prepare for Agent Execution

阶段1：准备Agent执行

Input: Execution sequence document
  1. Select batch for agent execution:
    • Identify next uncompleted batch
    • Confirm all dependencies are met
    • Check for any blockers from previous batches
    • If blockers exist, resolve before proceeding
  2. Prepare batch context:
    • Extract all tasks in this batch
    • Include acceptance criteria for each task
    • Document any integration points
    • List dependencies and what tasks feed into this batch
  3. Create agent prompt:
    • Clear objective: "Execute these N tasks"
    • Task list with descriptions and acceptance criteria
    • Integration points and expected outputs
    • Success criteria for this batch
    • Known risks or technical complexity
输入：执行序列文档
  1. 选择待执行的任务批次：
    • 确定下一个未完成的批次
    • 确认所有依赖条件已满足
    • 检查上一批次是否存在阻塞问题
    • 如果有阻塞问题，先解决再继续
  2. 准备批次上下文信息：
    • 提取该批次的所有任务
    • 包含每个任务的验收标准
    • 记录所有集成点
    • 列出依赖关系以及为该批次提供输入的任务
  3. 创建Agent提示词：
    • 明确目标：“执行以下N项任务”
    • 带描述和验收标准的任务列表
    • 集成点和预期输出
    • 该批次的成功标准
    • 已知风险或技术复杂度

Phase 2: Agent Executes Batch

阶段2：Agent执行批次任务

Agent actions:
  • Receive batch with clear task list
  • Execute tasks in sequence or parallel (as specified)
  • Verify each task meets acceptance criteria
  • Test integration with previous work
  • Document completion and any issues
You monitor:
  • Agent progress during execution
  • Any failures or unexpected issues
  • Blockers that emerge
  • Quality of implementation
Agent操作：
  • 接收带清晰任务列表的批次信息
  • 按指定顺序或并行执行任务
  • 验证每个任务是否符合验收标准
  • 测试与之前工作的集成情况
  • 记录完成情况和所有问题
你的监控工作：
  • Agent执行期间的进度
  • 任何失败或意外问题
  • 出现的阻塞问题
  • 实现质量

Phase 3: Verify Batch Completion

阶段3：验证批次完成情况

  1. Check task completion:
    • Does each task meet its acceptance criteria?
    • Are integration points working?
    • Any test failures?
    • Code quality acceptable?
  2. Identify issues:
    • What didn't work as expected?
    • What needs rework?
    • What assumptions were wrong?
  3. Update progress:
    • Mark completed tasks as ✅
    • Mark tasks needing rework as 🔄
    • Mark any new blockers as 🔴
    • Document what worked well
  1. 检查任务完成状态：
    • 每个任务是否满足验收标准？
    • 集成点是否正常工作？
    • 是否存在测试失败？
    • 代码质量是否达标？
  2. 识别问题：
    • 哪些工作未按预期执行？
    • 哪些内容需要返工？
    • 哪些假设是错误的？
  3. 更新进度：
    • 将已完成任务标记为 ✅
    • 将需要返工的任务标记为 🔄
    • 将新发现的阻塞问题标记为 🔴
    • 记录运行良好的内容

Phase 4: Identify and Track Blockers

阶段4：识别并跟踪阻塞问题

  1. Classify blockers:
    • Technical: Feature doesn't work as designed
    • Integration: Task output doesn't match what next task needs
    • Design: Requirements were unclear or wrong
    • External: Waiting on something outside the feature (dependency, library, API)
  2. Document blocker:
    • What's preventing progress?
    • Which tasks are blocked?
    • Root cause (if known)?
    • How long to resolve?
  3. Resolution path:
    • Can it be fixed immediately? (do it)
    • Does it need design change? (clarify then rework)
    • Is it external? (document and wait, or work around)
  1. 分类阻塞问题：
    • 技术类：功能未按设计要求工作
    • 集成类：任务输出不符合下一个任务的需求
    • 设计类：需求不明确或存在错误
    • 外部类：等待功能外的内容（依赖项、库、API）
  2. 记录阻塞问题：
    • 是什么阻碍了进度？
    • 哪些任务被阻塞？
    • 根本原因（如果已知）？
    • 解决所需时间？
  3. 解决路径：
    • 是否可以立即修复？（执行修复）
    • 是否需要更改设计？（先明确需求再返工）
    • 是否为外部依赖？（记录并等待，或寻找替代方案）

Phase 5: Plan Next Batch

阶段5：规划下一个批次

  1. Review current state:
    • What's completed ✅
    • What's in progress 🔄
    • What's blocked 🔴
    • What's ready to start ⏭️
  2. Select next batch:
    • Find next batch with all dependencies met
    • Check for any blockers from previous work
    • Prepare batch context (same as Phase 1)
  3. Brief next agent:
    • Pass execution progress
    • Identify any issues from previous batch
    • Provide clear task list for next batch
    • Highlight integration expectations
  1. 回顾当前状态：
    • 已完成 ✅
    • 进行中 🔄
    • 已阻塞 🔴
    • 即将启动 ⏭️
  2. 选择下一个批次：
    • 找到所有依赖条件已满足的下一个批次
    • 检查之前的工作是否存在阻塞问题
    • 准备批次上下文信息（同阶段1）
  3. 向下一个Agent做工作说明：
    • 传递执行进度信息
    • 指出上一批次的所有问题
    • 提供下一批次的清晰任务列表
    • 强调集成预期

Phase 6: Track Overall Progress

阶段6：跟踪整体进度

Maintain live progress document showing:
  • Completed batches: Which are done ✅
  • Current batch: What agent is working on now 🔄
  • Ready batches: What's queued next ⏭️
  • Blocked: What can't proceed and why 🔴
  • Overall %: How close to done
维护实时进度文档，展示：
  • 已完成批次：哪些已完成 ✅
  • 当前批次：Agent正在处理的内容 🔄
  • 待启动批次：下一个待执行的内容 ⏭️
  • 已阻塞内容：无法推进的内容及原因 🔴
  • 整体完成度：距离完成的进度

Output Format: Execution Progress

输出格式：执行进度文档

Create/update file: 
docs/features/[feature-name]/implementation-progress.md
Directory: 
docs/features/[feature-name]/

Filename: 
implementation-progress.md
(clear, representative name)
Example: 
docs/features/user-authentication/implementation-progress.md
markdown
undefined
创建/更新文件：
docs/features/[feature-name]/implementation-progress.md
目录：
docs/features/[feature-name]/

文件名：
implementation-progress.md
（清晰、具有代表性的名称）
示例：
docs/features/user-authentication/implementation-progress.md
markdown
undefined

Execution Progress: [Feature Name]

执行进度：[功能名称]

Last Updated: [Date/Time] Overall Progress: [X]% complete ([N] of [Total] tasks done)
最后更新时间：[日期/时间] 整体进度：[X]% 完成（总任务数[Total]，已完成[N]项）

Status Summary

状态汇总

StatusCountExamples
✅ Complete[N]Task 1, Task 3, Task 5
🔄 In Progress[N]Task 2 (Agent Session X)
⏭️ Ready to Start[N]Task 4, Task 6
🔴 Blocked[N]Task 7 (waiting for Task 2)
⚠️ Rework Needed[N]Task 8 (test failure)
状态数量示例
✅ 已完成[N]任务1、任务3、任务5
🔄 进行中[N]任务2（Agent会话X）
⏭️ 待启动[N]任务4、任务6
🔴 已阻塞[N]任务7（等待任务2完成）
⚠️ 需要返工[N]任务8（测试失败）

Completed Batches ✅

已完成批次 ✅

Batch 1: [Name]

批次1：[名称]

  • Completed: [Date]
  • Tasks: [List all tasks]
  • Status: ✅ All tasks passed acceptance criteria
  • Issues: None / [List any issues found and fixed]
  • Integration: Working correctly with Batch 2
  • Handoff: [What does next batch need to know?]
  • 完成时间：[日期]
  • 任务列表：[列出所有任务]
  • 状态：✅ 所有任务均通过验收标准
  • 问题：无 / [列出发现并修复的问题]
  • 集成情况：与批次2正常集成
  • 交接说明：[下一批次需要了解的内容]

Batch 2: [Name]

批次2：[名称]

  • Completed: [Date]
  • Tasks: [List all tasks]
  • Status: ✅ Complete, [N] test failures resolved
  • Issues: [Describe any issues]
  • Integration: [Status]
  • Handoff: [What does next batch need to know?]
  • 完成时间：[日期]
  • 任务列表：[列出所有任务]
  • 状态：✅ 完成，已解决[N]个测试失败问题
  • 问题：[描述所有问题]
  • 集成情况：[状态]
  • 交接说明：[下一批次需要了解的内容]

Current Batch 🔄

当前批次 🔄

Batch [N]: [Name]

批次[N]：[名称]

  • Started: [Date]
  • Assigned To: [Agent/Session]
  • Tasks:
    • Task [ID]: [Title] - [% complete]
    • Task [ID]: [Title] - [% complete]
  • Expected Completion: [Date/time estimate]
  • Issues Encountered:
    • [Issue 1]: [Description and status]
    • [Issue 2]: [Description and status]
  • Integration Points: [What needs to work with previous batch?]
  • 启动时间：[日期]
  • 分配对象：[Agent/会话]
  • 任务列表：
    • 任务[ID]：[标题] - [% 完成]
    • 任务[ID]：[标题] - [% 完成]
  • 预计完成时间：[日期/时间估算]
  • 遇到的问题：
    • [问题1]：[描述和状态]
    • [问题2]：[描述和状态]
  • 集成点：[需要与上一批次集成的内容]

Ready to Start ⏭️

待启动 ⏭️

Batch [N]: [Name]

批次[N]：[名称]

  • Dependencies: All met ✅
  • Blockers: None
  • Tasks: [List N tasks]
  • Expected Start: [When agent will pick this up]
  • 依赖条件：全部满足 ✅
  • 阻塞问题：无
  • 任务列表：[列出N项任务]
  • 预计启动时间：[Agent将接手的时间]

Batch [N+1]: [Name]

批次[N+1]：[名称]

  • Dependencies: [Status]
  • Blockers: [Any known issues?]
  • Tasks: [List N tasks]
  • Ready: [Date it will be ready]
  • 依赖条件：[状态]
  • 阻塞问题：[是否存在已知问题？]
  • 任务列表：[列出N项任务]
  • 待启动时间：[准备就绪的日期]

Blocked 🔴

已阻塞 🔴

Task [ID]: [Title]

任务[ID]：[标题]

  • Blocker: [What's preventing completion?]
  • Depends On: [Task X - not complete yet]
  • Impact: [What does this block?]
  • Resolution: [When will dependency be done?]
  • 阻塞原因：[阻碍完成的因素]
  • 依赖项：[任务X - 尚未完成]
  • 影响范围：[该问题阻塞了哪些内容？]
  • 解决时间：[依赖项预计完成时间]

Blockers Log

阻塞问题日志

See 
[feature-name]-blockers.md
for detailed blocker tracking.
Summary:
  • Critical blockers: [N]
  • High priority: [N]
  • Medium: [N]
  • Waiting for: [External dependency X, Design decision Y, etc.]
详细阻塞问题跟踪请查看
[feature-name]-blockers.md
。
汇总：
  • 严重阻塞问题：[N]
  • 高优先级：[N]
  • 中优先级：[N]
  • 等待内容：[外部依赖X、设计决策Y等]

Recent Session Summaries

近期会话总结

Session [Date] - Agent [Name/Type]

会话[日期] - Agent[名称/类型]

  • Batch Executed: [Batch name]
  • Tasks Completed: [List]
  • Tests Passed: [N] / [N]
  • Issues Found: [List any]
  • Code Quality: [Assessment]
  • Handoff Notes: [What next agent needs to know]
  • 执行批次：[批次名称]
  • 完成任务：[列表]
  • 通过测试数：[N] / [N]
  • 发现的问题：[列出所有问题]
  • 代码质量：[评估结果]
  • 交接说明：[下一个Agent需要了解的内容]

Session [Previous Date]

会话[上一个日期]

  • [Previous session summary]
  • [上一个会话总结]

Critical Path Status

关键路径状态

Tasks that determine feature completion:
  • Task [ID]: ✅ Complete
  • Task [ID]: 🔄 In Progress (Agent Session X)
  • Task [ID]: ⏭️ Ready (starting [Date])
Overall critical path: On track / At risk / Behind
决定功能完成时间的任务：
  • 任务[ID]：✅ 已完成
  • 任务[ID]：🔄 进行中（Agent会话X）
  • 任务[ID]：⏭️ 待启动（启动日期[Date]）
整体关键路径状态：按计划推进 / 存在风险 / 进度滞后

Next Actions

下一步行动

  1. [Action 1]: By [Date]
  2. [Action 2]: By [Date]
  3. [Action 3]: By [Date]
undefined
  1. [行动1]：完成时间[日期]
  2. [行动2]：完成时间[日期]
  3. [行动3]：完成时间[日期]
undefined

Output Format: Blocker Log

输出格式：阻塞问题日志

Create/update file: 
docs/features/[feature-name]/blockers.md
Directory: 
docs/features/[feature-name]/

Filename: 
blockers.md
(clear, representative name)
Example: 
docs/features/user-authentication/blockers.md
markdown
undefined
创建/更新文件：
docs/features/[feature-name]/blockers.md
目录：
docs/features/[feature-name]/

文件名：
blockers.md
（清晰、具有代表性的名称）
示例：
docs/features/user-authentication/blockers.md
markdown
undefined

Blocker Log: [Feature Name]

阻塞问题日志：[功能名称]

Current Blockers 🔴

当前阻塞问题 🔴

Blocker 1: [Title]

阻塞问题1：[标题]

Severity: Critical / High / Medium
Affected Tasks: Task [ID], Task [ID]
Description: [What's blocking progress?]
Cause: [Why is this happening?]
Impact: [If not resolved, what doesn't get built?]
Resolution: [How will this be fixed?]
Owner: [Your role, or external dependency name]
Target Resolution: [Date/time]
严重程度：严重 / 高 / 中
影响任务：任务[ID]、任务[ID]
描述：[阻碍进度的具体内容]
原因：[问题产生的原因]
影响：[若不解决，哪些内容无法构建？]
解决方式：[如何修复该问题？]
负责人：[你的角色，或外部依赖名称]
预计解决时间：[日期/时间]

Recently Resolved ✅

近期已解决阻塞问题 ✅

Blocker: [Title]

阻塞问题：[标题]

Reported: [Date] Resolved: [Date] (resolved in [Duration])
Cause: [What was the issue?]
Solution: [How was it fixed?]
Lessons: [What did we learn?]
上报时间：[日期] 解决时间：[日期]（耗时[Duration]）
原因：[问题是什么？]
解决方案：[如何修复的？]
经验教训：[我们学到了什么？]

External Blockers ⏸️

外部阻塞问题 ⏸️

Waiting on things outside this feature:
  • [Dependency/Library]: Waiting for [What?] - Expected [Date]
  • [External Service]: [Status] - Expected [Date]
undefined
等待功能外的内容：
  • [依赖项/库]：等待[内容] - 预计[日期]
  • [外部服务]：[状态] - 预计[日期]
undefined

Session Handoff Format

会话交接格式

After each agent session, create brief summary in feature directory:
File path: 
docs/features/[feature-name]/session-summary-[batch-num].md

Filename pattern: 
session-summary-1.md
, 
session-summary-2.md
, etc.
Example: 
docs/features/user-authentication/session-summary-1.md
markdown
undefined
每个Agent会话结束后，在功能目录中创建简短总结：
文件路径：
docs/features/[feature-name]/session-summary-[batch-num].md

文件名规则：
session-summary-1.md
、
session-summary-2.md
等
示例：
docs/features/user-authentication/session-summary-1.md
markdown
undefined

Session Summary: Batch [N] - [Date]

会话总结：批次[N] - [日期]

Batch: [Batch name] Agent: [AI model/type used] Duration: [Session length]
批次：[批次名称] Agent：[使用的AI模型/类型] 时长：[会话时长]

Completed Tasks ✅

已完成任务 ✅

  • Task [ID]: [Title] - ✅ Complete, all acceptance criteria met
  • Task [ID]: [Title] - ✅ Complete, [N] test failures fixed
  • 任务[ID]：[标题] - ✅ 完成，所有验收标准均满足
  • 任务[ID]：[标题] - ✅ 完成，已修复[N]个测试失败问题

Tasks Needing Rework 🔄

需要返工的任务 🔄

  • Task [ID]: [Title] - Test failure: [Description]
    • Status: Being reworked
    • Expected completion: [When]
  • 任务[ID]：[标题] - 测试失败：[描述]
    • 状态：正在返工
    • 预计完成时间：[时间]

Blockers Encountered 🔴

遇到的阻塞问题 🔴

  • [Blocker description] - Added to blocker log
  • [阻塞问题描述] - 已添加至阻塞问题日志

Integration Status

集成状态

  • Previous batch: ✅ Working correctly
  • Next batch: ⏭️ Ready to start when this completes
  • 上一批次：✅ 集成正常
  • 下一批次：⏭️ 本批次完成后即可启动

Handoff for Next Agent

给下一个Agent的交接说明

[Copy what next agent needs to know]
  • What these tasks built
  • Any quirks or gotchas
  • Integration requirements
  • Files/paths that matter
undefined
[复制下一个Agent需要了解的内容]
  • 这些任务构建的内容
  • 任何特殊情况或注意事项
  • 集成要求
  • 重要的文件/路径
undefined

Guidelines

指导原则

Task Completion Criteria

任务完成标准

A task is ✅ COMPLETE when:
  • All acceptance criteria are met
  • Code is in repository (merged or staged)
  • Tests pass (if applicable)
  • Integration with previous work verified
  • No known issues
A task is 🔄 IN PROGRESS when:
  • Agent is actively building it
  • Some work is done but not all acceptance criteria met
  • Waiting on integration testing
A task is ⏭️ READY when:
  • All dependencies are complete
  • No blockers exist
  • Agent can start immediately
A task is 🔴 BLOCKED when:
  • Cannot proceed due to external dependency
  • Depends on incomplete task
  • Needs clarification or decision
任务标记为 ✅ 已完成的条件：
  • 所有验收标准均满足
  • 代码已存入代码仓库（已合并或暂存）
  • 测试通过（若适用）
  • 与之前工作的集成已验证
  • 无已知问题
任务标记为 🔄 进行中的条件：
  • Agent正在积极构建该任务
  • 已完成部分工作，但未满足所有验收标准
  • 等待集成测试
任务标记为 ⏭️ 待启动的条件：
  • 所有依赖项已完成
  • 无阻塞问题
  • Agent可立即启动
任务标记为 🔴 已阻塞的条件：
  • 因外部依赖无法推进
  • 依赖未完成的任务
  • 需要澄清或决策

Batch Sizing

批次规模

  • Too small: 1 task per batch (too granular)
  • Good size: 1-3 related tasks per batch (can complete in one session)
  • Too large: 4+ tasks (too much context, may not complete)
  • 过小：每批次1个任务（粒度太细）
  • 合适规模：每批次1-3个相关任务（可在一个会话内完成）
  • 过大：每批次4个及以上任务（上下文过多，可能无法在一个会话内完成）

Blocker Resolution

阻塞问题解决

Immediate fixes:
  • Rework task: Have agent fix it
  • Clarify requirements: Get clear spec, agent redoes task
  • Code quality: Agent improves, retests
Wait & Proceed:
  • External dependency: Work on other batches, revisit later
  • Design decision: Move to next batch while waiting
  • Known limitation: Document and proceed
Cannot Proceed:
  • Critical blocker with no workaround: Stop, resolve, continue
立即修复：
  • 返工任务：让Agent修复
  • 澄清需求：获取清晰规格，让Agent重新执行任务
  • 代码质量：Agent优化代码并重新测试
等待并推进其他工作：
  • 外部依赖：先处理其他批次，之后再回来处理
  • 设计决策：等待期间推进下一批次
  • 已知限制：记录并继续推进
无法推进：
  • 无替代方案的严重阻塞问题：停止工作，解决后再继续

Common Patterns

常见场景

Pattern: Task Fails Tests

场景：任务测试失败

  1. Agent reports: "Test X failed"
  2. You: Review failure, identify cause
  3. Either: Rework task, or clarify requirements
  4. Agent: Re-executes task
  5. Update progress when fixed
  1. Agent报告：“测试X失败”
  2. 你：查看失败原因，确定问题根源
  3. 选择：要么返工任务，要么澄清需求
  4. Agent：重新执行任务
  5. 修复后更新进度

Pattern: Dependencies Not Met

场景：依赖条件未满足

  1. Agent reports: "Can't start because Task X not done"
  2. You: Verify Task X completion
  3. If complete: Task needs output from Task X (integration issue)
  4. If incomplete: Move this batch down, work on different batch
  5. Return to blocked task when dependency ready
  1. Agent报告：“无法启动，因为任务X未完成”
  2. 你：验证任务X的完成状态
  3. 若已完成：任务需要任务X的输出（集成问题）
  4. 若未完成：将该批次延后，处理其他批次
  5. 依赖项就绪后再返回处理阻塞任务

Pattern: Integration Breaks

场景：集成失败

  1. Agent reports: "Task works alone, breaks when integrated"
  2. You: Review what task outputs vs. what next task expects
  3. Either: Fix task implementation, or fix integration point
  4. Agent: Tests integration again
  5. Mark complete only when integrated successfully
  1. Agent报告：“任务单独运行正常，但集成时失败”
  2. 你：查看任务输出与下一个任务预期输入的差异
  3. 选择：要么修复任务实现，要么修复集成点
  4. Agent：重新测试集成情况
  5. 仅当集成成功后才标记任务为完成

See Also

参考文档

Reference documents:
  • batch-execution-template.md
    : Template for batch execution
  • blocker-triage-guide.md
    : How to handle different blocker types
  • example-ai-implementation.md
    : Complete end-to-end example with User Authentication system
参考文档：
  • batch-execution-template.md
    ：批次执行模板
  • blocker-triage-guide.md
    ：不同类型阻塞问题的处理指南
  • example-ai-implementation.md
    ：用户认证系统完整端到端示例