@fitlab-ai/agent-infra 0.6.5 → 0.7.1

package/templates/.agents/skills/review-code/reference/report-template.zh-CN.md

@@ -0,0 +1,91 @@
+# 审查报告模板
+
+编写 `review-code.md` 或 `review-code-r{N}.md` 时使用本模板。
+
+## 输出模板
+
+```markdown
+# 代码审查报告
+
+- **审查轮次**：第 {review-round} 轮
+- **产物文件**：`{review-artifact}`
+- **审查输入**：
+  - `{code-artifact}`
+  - `{code-artifact}`（如存在）
+
+## 状态核对
+
+> 粘贴状态核对命令原文；每条命令以 `$ ` 开头。
+
+## 审查摘要
+
+- **审查者**：{reviewer-name}
+- **审查时间**：{timestamp}
+- **审查范围**：{file-count and major modules}
+- **总体结论**：{通过 / 需要修改 / 拒绝}（恰取一个；禁止写组合短语，否则 verify gate 失败）
+- **发现（AI 可处理）**：0 阻塞项，0 主要，0 次要 / **env-blocked**：0
+
+## 问题清单
+
+### 阻塞项（必须修复）
+
+#### 1. {问题标题}
+**文件**：`{file-path}:{line-number}`
+**说明**：{details}
+**修复建议**：{fix suggestion}
+
+### 主要问题（建议修复）
+
+#### 1. {问题标题}
+**文件**：`{file-path}:{line-number}`
+**说明**：{details}
+**修复建议**：{fix suggestion}
+
+### 次要问题（可选改进）
+
+#### 1. {改进点}
+**文件**：`{file-path}:{line-number}`
+**建议**：{improvement suggestion}
+
+## 环境性遗留
+
+> AI agent 在本执行环境无法闭环的项；不参与下一轮 refine。维护者在 PR description 中以「待人工验证」清单承接。
+
+#### 1. {环境性项标题}
+**文件**：`{file-path}:{line-number}`（如适用）
+**说明**：{details}
+**所需环境**：{e.g. Docker 沙箱 / macOS host / 特权 root / 第三方账号}
+**待人工执行的验证步骤**：{steps for the human verifier}
+
+> 如本轮无 env-blocked 项，保留段落标题并写「（无）」。
+
+
+## 证据原文
+
+> 每条“我验证了 X”断言都要配对对应 tool output 原文；gate 仅校验本段存在和至少一行 `$ `。
+
+- 断言：{verified claim}
+```text
+$ {command}
+{raw output}
+```
+
+## 亮点
+
+- {what went well}
+
+## 与方案一致性
+
+- [ ] 实现与技术方案一致
+- [ ] 没有意外的范围扩张
+
+## 结论与建议
+
+### 审查决定
+- [ ] 通过
+- [ ] 需要修改
+- [ ] 拒绝
+
+### 下一步
+{recommended next step}
+```

package/templates/.agents/skills/review-code/reference/review-criteria.en.md

@@ -0,0 +1,48 @@
+# Review Criteria
+
+Read this file before reviewing code or classifying finding severity.
+
+## Code Review
+
+Follow the `code-review` step in `.agents/workflows/feature-development.yaml`.
+
+**Required review areas**:
+- [ ] Code quality and project style
+- [ ] Bugs and risk identification
+- [ ] Test coverage and test quality
+- [ ] Error handling and edge cases
+- [ ] Performance and security risks
+- [ ] Comments and documentation
+- [ ] Consistency with the approved technical plan
+
+**Common anti-examples**:
+- Checking only whether tests pass without reading the actual diff
+- Treating wording preferences as reproducible code problems
+- Misclassifying environment-limited verification gaps as blockers
+
+## Common Review Principles
+
+1. **Strict but fair**: identify issues and acknowledge solid work
+2. **Specific**: cite exact file paths and line numbers
+3. **Actionable**: suggest a concrete fix
+4. **Severity-based**: clearly distinguish blockers, major issues, and minor issues
+
+## Environment-Blocked Classification
+
+Some findings cannot be closed by an AI agent in the current execution environment, for example:
+
+- Missing Docker / sandbox access for end-to-end validation
+- Missing a specific OS for macOS-only behavior
+- Missing third-party accounts / OAuth
+- Missing privileged operations such as root, sudo, or special network access
+
+**Decision tree**: "Can the AI agent close this item independently without changing the environment?"
+- Yes -> blocker / major / minor, based on risk
+- No -> **env-blocked** (a meta-category, not part of severity ordering)
+
+Where env-blocked items go:
+- Record them in an independent review report section named "Environment-Blocked Findings"
+- Include them at the end of the numeric summary, for example `(+ 1 env-blocked)`
+- Do **not** include them in the code-task fix loop; maintainers carry them in the PR description under manual verification
+
+Also inspect `git diff`, the latest code artifact, latest technical-plan review artifact, and `task.md` Activity Log so the report reflects the full change context.

package/templates/.agents/skills/{review-task → review-code}/reference/review-criteria.zh-CN.md

@@ -13,9 +13,15 @@
 - [ ] 错误处理和边界情况
 - [ ] 性能与安全风险
 - [ ] 代码注释和文档
-- [ ] 与技术方案的一致性
+- [ ] 与已批准技术方案的一致性
+
+**常见反例**：
+- 只检查测试是否通过，没有阅读实际 diff
+- 用自然语言措辞偏好替代可复现的代码问题
+- 把环境缺失导致无法验证的事项误归类为 blocker
+
+## 通用审查原则
 
-**审查原则**：
 1. **严格但公正**：既要指出问题，也要承认做得好的部分
 2. **具体**：引用准确的文件路径和行号
 3. **可执行**：给出明确可落地的修复建议
@@ -37,6 +43,6 @@
 env-blocked 项的去向：
 - 写入 review 报告独立段落「环境性遗留」
 - 在数字摘要末尾附带显示（如 `(+ 1 env-blocked)`）
-- **不**进入 refine 循环；维护者在 PR description 中以「待人工验证」清单形式承接
+- **不**进入 code-task 修复循环；维护者在 PR description 中以「待人工验证」清单形式承接
 
-同时检查 `git diff`，确保报告反映完整的变更上下文。
+同时检查 `git diff`、最新实现产物、最新技术方案审查产物和 `task.md` Activity Log，确保报告反映完整的变更上下文。

package/templates/.agents/skills/review-plan/SKILL.en.md

@@ -0,0 +1,80 @@
+---
+name: review-plan
+description: "Review the technical plan"
+---
+
+# Technical Plan Review
+
+Review the latest plan artifact and produce `review-plan.md` or `review-plan-r{N}.md`.
+
+## Boundary / Critical Rules
+
+- This skill only reviews plan artifacts and writes a report; it does not modify product code.
+- After executing this skill, you **must** immediately update task.md.
+
+Version stamp rule: when creating or updating `task.md` frontmatter, read `.agents/rules/version-stamp.md` first and write or refresh `agent_infra_version`.
+
+## Step 0: State Check (pre-execution hard gate)
+
+After loading workflow / skill / rules instructions, and before any task-state judgment or user-visible conclusion, run the state check first.
+
+Run these commands and paste the raw output into both the user-facing reply and this round's `## State Check` section:
+
+```bash
+git status -s
+ls -la .agents/workspace/active/{task-id}/
+tail .agents/workspace/active/{task-id}/task.md
+```
+
+## Task id short ref
+
+> If `{task-id}` begins with `#`, follow the "SKILL parameter resolver" section of `.agents/rules/task-short-id.md`; treat `{task-id}` as the resolved full `TASK-YYYYMMDD-HHMMSS` form for every downstream command.
+
+## Steps
+
+### 1. Verify Prerequisites
+
+Require `task.md` and at least one plan artifact: `plan.md` or `plan-r{N}.md`.
+
+### 2. Determine Review Round
+
+Record `{plan-artifact}`, `{review-round}`, and `{review-artifact}` (`review-plan.md` or `review-plan-r{N}.md`).
+
+### 3. Read Plan Context
+
+Read `{plan-artifact}`, the latest analysis artifact, `task.md`, and Issue context when available.
+
+### 4. Perform Review
+
+Check simplicity, executability, risk control, test strategy, file coverage, and phase boundaries.
+
+> Read `reference/review-criteria.md` before this step.
+
+### 5. Write Review Report
+
+Create `.agents/workspace/active/{task-id}/{review-artifact}`.
+
+> Read `reference/report-template.md` before writing the report.
+
+### 6. Update Task Status
+
+Get the current time:
+
+```bash
+date "+%Y-%m-%d %H:%M:%S%:z"
+```
+
+Set `current_step` to `technical-design-review`, refresh task metadata, and append:
+`- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Plan Review (Round {N})** by {agent} — Verdict: {Approved/Changes Requested/Rejected}, blockers: {n}, major: {n}, minor: {n}[ (+ {n} env-blocked)] → {review-artifact}`
+
+If task.md has a valid `issue_number`, read `.agents/rules/issue-sync.md`, sync the task comment, and publish the `{review-artifact}` comment.
+
+### 7. Run Completion Gate
+
+```bash
+node .agents/scripts/validate-artifact.js gate review-plan .agents/workspace/active/{task-id} {review-artifact} --format text
+```
+
+### 8. Tell the User
+
+Use the conclusion branch in `reference/output-templates.md` and show all TUI command formats.

package/templates/.agents/skills/review-plan/SKILL.zh-CN.md

@@ -0,0 +1,105 @@
+---
+name: review-plan
+description: "审查技术方案"
+---
+
+# 技术方案审查
+
+审查最新技术方案产物，并产出 `review-plan.md` 或 `review-plan-r{N}.md`。
+
+## 行为边界 / 关键规则
+
+- 本技能只审查方案产物并写报告，不修改业务代码
+- 执行本技能后，你**必须**立即更新 task.md
+
+版本戳规则：创建或更新 `task.md` frontmatter 时，先读取 `.agents/rules/version-stamp.md`，并写入或刷新 `agent_infra_version`。
+
+## 第 0 步：状态核对（执行前硬约束）
+
+在加载 workflow / skill / rules 指令之后、做任何任务状态判断或用户可见结论之前，必须先执行状态核对。指令类文件读取不算对外动作或结论。
+
+运行以下命令，并把原文粘贴到回复正文和本轮产物的 `## 状态核对` 段：
+
+```bash
+git status -s
+ls -la .agents/workspace/active/{task-id}/
+tail .agents/workspace/active/{task-id}/task.md
+```
+
+状态核对完成前，禁止任何关于外部状态的断言。
+
+## 任务入参短号别名
+
+> 如果 `{task-id}` 入参以 `#` 开头，先读取 `.agents/rules/task-short-id.md` 的「SKILL 入参解析」段执行解析；后续命令视 `{task-id}` 为解析后的全长 `TASK-YYYYMMDD-HHMMSS` 形式。
+
+## 执行步骤
+### 1. 验证前置条件
+
+要求存在：
+- `.agents/workspace/active/{task-id}/task.md`
+- 至少一个方案产物：`plan.md` 或 `plan-r{N}.md`
+
+### 2. 确定审查轮次
+
+扫描任务目录并记录：
+- `{plan-artifact}`：最高轮次的方案产物
+- `{review-round}`
+- `{review-artifact}`：`review-plan.md` 或 `review-plan-r{N}.md`
+
+### 3. 阅读方案上下文
+
+读取最新 `{plan-artifact}`、最新分析产物、`task.md` 和关联 Issue 上下文（如有）。
+
+### 4. 执行审查
+
+重点检查方案的简洁性、可执行性、风险控制、测试策略、文件清单和阶段边界。
+
+> 详细审查标准见 `reference/review-criteria.md`。执行此步骤前先读取 `reference/review-criteria.md`。
+
+### 5. 编写审查报告
+
+创建 `.agents/workspace/active/{task-id}/{review-artifact}`。
+
+> 报告格式见 `reference/report-template.md`。写报告前先读取 `reference/report-template.md`。
+
+### 6. 更新任务状态
+
+获取当前时间：
+
+```bash
+date "+%Y-%m-%d %H:%M:%S%:z"
+```
+
+更新 task.md：
+- `current_step`：technical-design-review
+- `assigned_to`：{当前代理}
+- `updated_at`：{当前时间}
+- `agent_infra_version`：按 `.agents/rules/version-stamp.md` 取值
+- 追加：
+  `- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Plan Review (Round {N})** by {agent} — Verdict: {Approved/Changes Requested/Rejected}, blockers: {n}, major: {n}, minor: {n}[ (+ {n} env-blocked)] → {review-artifact}`
+
+如果 task.md 中存在有效的 `issue_number`，执行前先读取 `.agents/rules/issue-sync.md`，完成 upstream 仓库检测和权限检测，然后同步 task 评论并发布 `{review-artifact}` 评论。
+
+### 7. 完成校验
+
+```bash
+node .agents/scripts/validate-artifact.js gate review-plan .agents/workspace/active/{task-id} {review-artifact} --format text
+```
+
+校验通过后继续告知用户；校验失败则修复报告或 task 状态后重跑。
+
+### 8. 告知用户
+
+按 `reference/output-templates.md` 的结论分支输出，并展示所有 TUI 的下一步命令。
+
+## 完成检查清单
+
+- [ ] 已审查最新方案上下文
+- [ ] 已创建 `{review-artifact}`
+- [ ] 已更新 task.md 并追加 Activity Log
+- [ ] 已展示所有 TUI 的下一步命令
+
+## 注意事项
+
+- 首轮审查使用 `review-plan.md`，后续轮次使用 `review-plan-r{N}.md`
+- 所有问题都要引用具体文件路径和行号；方案产物问题可引用 `{plan-artifact}` 的行号

package/templates/.agents/skills/{refine-task → review-plan}/config/verify.en.json

@@ -1,5 +1,5 @@
 {
-  "skill": "refine-task",
+  "skill": "review-plan",
   "checks": {
     "task-meta": {
       "required_fields": [
@@ -12,35 +12,39 @@
         "agent_infra_version",
         "current_step",
         "assigned_to"
-      ]
+      ],
+      "expected_step": "technical-design-review"
     },
     "artifact": {
-      "file_pattern": "refinement.md|refinement-r{N}.md",
+      "file_pattern": "review-plan.md|review-plan-r{N}.md",
       "required_sections": [
-        "Review Feedback Handling",
-        "Test Results After Refinement",
+        "Review Summary",
+        "Findings",
+        "Environment-Blocked Findings",
+        "Conclusion and Recommendations",
         "State Check",
         "Evidence"
       ],
-      "freshness_minutes": 30,
       "required_patterns": [
+        "^### Approval Decision$",
         "^\\$ "
-      ]
+      ],
+      "freshness_minutes": 30
     },
     "activity-log": {
-      "expected_action_pattern": "Refinement \\(Round \\d+, for .+\\)",
+      "expected_action_pattern": "Plan Review \\(Round \\d+\\)",
       "freshness_minutes": 30
     },
     "platform-sync": {
       "when": "issue_number_exists",
-      "expected_status_label": "status: in-progress",
+      "expected_status_label": "status: pending-design-work",
       "expected_comment_marker": "<!-- sync-issue:{task-id}:{artifact-stem} -->",
       "verify_comment_content": true,
       "verify_task_comment_content": true,
       "verify_issue_type": true,
       "verify_issue_fields": false,
       "verify_milestone": true,
-      "expected_status_label_key": "inProgress",
+      "expected_status_label_key": "pendingDesignWork",
       "expected_comment_marker_key": "artifact"
     }
   }

package/templates/.agents/skills/{refine-task → review-plan}/config/verify.zh-CN.json

@@ -1,5 +1,5 @@
 {
-  "skill": "refine-task",
+  "skill": "review-plan",
   "checks": {
     "task-meta": {
       "required_fields": [
@@ -12,35 +12,39 @@
         "agent_infra_version",
         "current_step",
         "assigned_to"
-      ]
+      ],
+      "expected_step": "technical-design-review"
     },
     "artifact": {
-      "file_pattern": "refinement.md|refinement-r{N}.md",
+      "file_pattern": "review-plan.md|review-plan-r{N}.md",
       "required_sections": [
-        "审查反馈处理",
-        "修复后的测试结果",
+        "审查摘要",
+        "问题清单",
+        "环境性遗留",
+        "结论与建议",
         "状态核对",
         "证据原文"
       ],
-      "freshness_minutes": 30,
       "required_patterns": [
+        "^### 审查决定$",
         "^\\$ "
-      ]
+      ],
+      "freshness_minutes": 30
     },
     "activity-log": {
-      "expected_action_pattern": "Refinement \\(Round \\d+, for .+\\)",
+      "expected_action_pattern": "Plan Review \\(Round \\d+\\)",
       "freshness_minutes": 30
     },
     "platform-sync": {
       "when": "issue_number_exists",
-      "expected_status_label": "status: in-progress",
+      "expected_status_label": "status: pending-design-work",
       "expected_comment_marker": "<!-- sync-issue:{task-id}:{artifact-stem} -->",
       "verify_comment_content": true,
       "verify_task_comment_content": true,
       "verify_issue_type": true,
       "verify_issue_fields": false,
       "verify_milestone": true,
-      "expected_status_label_key": "inProgress",
+      "expected_status_label_key": "pendingDesignWork",
       "expected_comment_marker_key": "artifact"
     }
   }

package/templates/.agents/skills/review-plan/reference/output-templates.en.md

@@ -0,0 +1,87 @@
+# Review Output Templates
+
+Read this file before presenting the final review result to the user.
+
+## Select exactly one output scenario
+
+Evaluate in this order (**env-blocked count does not participate in selection**):
+1. If `Blocker = 0`, `Major = 0`, and `Minor = 0`, use Scenario A, regardless of env-blocked count
+2. If `Blocker = 0` and (`Major > 0` or `Minor > 0`), use Scenario B
+3. If `Blocker > 0` and the issues can be handled by one focused revision, use Scenario C
+4. If the technical plan needs major redesign, broad rewriting, or a restart, use Scenario D
+
+Rules:
+- Do not skip scenario selection
+- Do not mix text from multiple scenarios
+- If `Blocker > 0`, never use an approved template
+- Never count env-blocked items as blocker / major / minor or use them to trigger Scenario B/C/D
+- The selected scenario must include all TUI command formats
+
+### Scenario A: Approved with no findings
+
+```text
+Task {task-id} technical plan review completed. Verdict: approved.
+- Blockers: 0 | Major issues: 0 | Minor issues: 0[ | Environment-blocked: {n} (outside AI fix scope)]
+[- Review report: .agents/workspace/active/{task-id}/{review-artifact}]
+
+Next step - write code:
+  - Claude Code / OpenCode: /code-task {task-id}
+  - Gemini CLI: /agent-infra:code-task {task-id}
+  - Codex CLI: $code-task {task-id}
+
+[When env-blocked > 0, append:]
+Reminder: env-blocked items belong in the PR description manual verification checklist and should not trigger /plan-task.
+```
+
+### Scenario B: Approved with findings
+
+```text
+Task {task-id} technical plan review completed. Verdict: approved.
+- Blockers: 0 | Major issues: {n} | Minor issues: {n}[ | Environment-blocked: {n} (outside AI fix scope)]
+- Review report: .agents/workspace/active/{task-id}/{review-artifact}
+
+Next step - revise plan before coding (recommended):
+  - Claude Code / OpenCode: /plan-task {task-id}
+  - Gemini CLI: /agent-infra:plan-task {task-id}
+  - Codex CLI: $plan-task {task-id}
+
+Or proceed directly to coding:
+  - Claude Code / OpenCode: /code-task {task-id}
+  - Gemini CLI: /agent-infra:code-task {task-id}
+  - Codex CLI: $code-task {task-id}
+
+[When env-blocked > 0, append:]
+Reminder: env-blocked items belong in the PR description manual verification checklist and should not trigger /plan-task.
+```
+
+### Scenario C: Changes requested
+
+```text
+Task {task-id} technical plan review completed. Verdict: changes requested.
+- Blockers: {n} | Major issues: {n} | Minor issues: {n}[ | Environment-blocked: {n} (outside AI fix scope)]
+- Review report: .agents/workspace/active/{task-id}/{review-artifact}
+
+Next step - revise technical plan:
+  - Claude Code / OpenCode: /plan-task {task-id}
+  - Gemini CLI: /agent-infra:plan-task {task-id}
+  - Codex CLI: $plan-task {task-id}
+
+[When env-blocked > 0, append:]
+Reminder: env-blocked items belong in the PR description manual verification checklist and should not trigger /plan-task.
+```
+
+### Scenario D: Rejected
+
+```text
+Task {task-id} technical plan review completed. Verdict: rejected, redesign required.
+- Blockers: {n} | Major issues: {n} | Minor issues: {n}[ | Environment-blocked: {n} (outside AI fix scope)]
+- Review report: .agents/workspace/active/{task-id}/{review-artifact}
+
+Next step - redesign:
+  - Claude Code / OpenCode: /plan-task {task-id}
+  - Gemini CLI: /agent-infra:plan-task {task-id}
+  - Codex CLI: $plan-task {task-id}
+
+[When env-blocked > 0, append:]
+Reminder: env-blocked items belong in the PR description manual verification checklist and should not trigger /plan-task.
+```

package/templates/.agents/skills/review-plan/reference/output-templates.zh-CN.md

@@ -0,0 +1,87 @@
+# 审查输出模板
+
+在向用户汇报最终审查结论之前先读取本文件。
+
+## 选择唯一输出场景
+
+按以下顺序判断（**注意：env-blocked 数量不参与判断**）：
+1. 如果 `Blocker = 0` 且 `Major = 0` 且 `Minor = 0`，使用场景 A（不管 env-blocked 是否 > 0）
+2. 如果 `Blocker = 0` 且（`Major > 0` 或 `Minor > 0`），使用场景 B
+3. 如果 `Blocker > 0`，且问题可以通过一次聚焦修复解决，使用场景 C
+4. 如果技术方案需要重大重构、大范围重写或整体重来，使用场景 D
+
+禁止规则：
+- 不要跳过场景判断步骤
+- 不要混用不同场景的文案
+- 只要 `Blocker > 0`，就绝对不能输出通过模板
+- env-blocked 项绝对不能被计入 blocker / major / minor 计数，也不能用作触发场景 B/C/D 的依据
+- 所选场景中必须包含所有 TUI 命令格式
+
+### 场景 A：通过且无问题
+
+```text
+任务 {task-id} 技术方案审查完成。结论：通过。
+- 阻塞项：0 | 主要问题：0 | 次要问题：0[ | 环境性遗留：{n}（不在 AI 修复范围）]
+[- 审查报告：.agents/workspace/active/{task-id}/{review-artifact}]
+
+下一步 - 编写代码：
+  - Claude Code / OpenCode：/code-task {task-id}
+  - Gemini CLI：/agent-infra:code-task {task-id}
+  - Codex CLI：$code-task {task-id}
+
+[当 env-blocked > 0 时，在最后附加一行：]
+提醒：env-blocked 项需在 PR description 的「待人工验证」清单中承接，不应触发 /plan-task。
+```
+
+### 场景 B：通过但有问题
+
+```text
+任务 {task-id} 技术方案审查完成。结论：通过。
+- 阻塞项：0 | 主要问题：{n} | 次要问题：{n}[ | 环境性遗留：{n}（不在 AI 修复范围）]
+- 审查报告：.agents/workspace/active/{task-id}/{review-artifact}
+
+下一步 - 修订方案后编码（推荐）：
+  - Claude Code / OpenCode：/plan-task {task-id}
+  - Gemini CLI：/agent-infra:plan-task {task-id}
+  - Codex CLI：$plan-task {task-id}
+
+或直接进入编码：
+  - Claude Code / OpenCode：/code-task {task-id}
+  - Gemini CLI：/agent-infra:code-task {task-id}
+  - Codex CLI：$code-task {task-id}
+
+[当 env-blocked > 0 时，在最后附加一行：]
+提醒：env-blocked 项需在 PR description 的「待人工验证」清单中承接，不应触发 /plan-task。
+```
+
+### 场景 C：需要修改
+
+```text
+任务 {task-id} 技术方案审查完成。结论：需要修改。
+- 阻塞项：{n} | 主要问题：{n} | 次要问题：{n}[ | 环境性遗留：{n}（不在 AI 修复范围）]
+- 审查报告：.agents/workspace/active/{task-id}/{review-artifact}
+
+下一步 - 修订技术方案：
+  - Claude Code / OpenCode：/plan-task {task-id}
+  - Gemini CLI：/agent-infra:plan-task {task-id}
+  - Codex CLI：$plan-task {task-id}
+
+[当 env-blocked > 0 时，在最后附加一行：]
+提醒：env-blocked 项需在 PR description 的「待人工验证」清单中承接，不应触发 /plan-task。
+```
+
+### 场景 D：拒绝
+
+```text
+任务 {task-id} 技术方案审查完成。结论：拒绝，需要重新设计。
+- 阻塞项：{n} | 主要问题：{n} | 次要问题：{n}[ | 环境性遗留：{n}（不在 AI 修复范围）]
+- 审查报告：.agents/workspace/active/{task-id}/{review-artifact}
+
+下一步 - 重新设计：
+  - Claude Code / OpenCode：/plan-task {task-id}
+  - Gemini CLI：/agent-infra:plan-task {task-id}
+  - Codex CLI：$plan-task {task-id}
+
+[当 env-blocked > 0 时，在最后附加一行：]
+提醒：env-blocked 项需在 PR description 的「待人工验证」清单中承接，不应触发 /plan-task。
+```