@fitlab-ai/agent-infra 0.6.5 → 0.7.0

package/templates/.agents/skills/import-issue/SKILL.en.md

@@ -25,7 +25,7 @@ Use the Issue title as-is for the task title (preserve the Issue's original lang
 ### 2. Check for an Existing Task
 
 2.1 Search `.agents/workspace/active/` for an existing task linked to this Issue.
-- If found, ask the user whether to re-import or continue with the existing task
+- If found, **reuse the existing task by default** (Scenario A); do not ask the user. State clearly in the final notice: "Reused existing task `{task-id}`; not re-imported." If the user wants to re-import, they must first archive or delete the existing task and run this skill again
 - If not found, continue to 2.2
 
 2.2 Use the "historical task comment scan" command in `.agents/rules/issue-pr-commands.md` to scan Issue comments for sync markers and look for a recoverable historical task ID.
@@ -44,7 +44,7 @@ Exit code handling for the whole pipeline:
 
 | Scenario | Trigger | task ID source | created_at source | User confirmation |
 |---|---|---|---|---|
-| Scenario A | 2.1 finds a local task | Reuse local ID | Preserve local value | Must ask whether to re-import or continue using the existing task |
+| Scenario A | 2.1 finds a local task | Reuse local ID | Preserve local value | Reuse by default; do not ask; inform the user reuse happened |
 | Scenario B | 2.1 no match + 2.2 no candidate | Create with `date +%Y%m%d-%H%M%S` | Current time | Not required |
 | Scenario C | 2.1 no match + 2.2 any candidate | Automatically reuse the earliest candidate ID | Prefer remote frontmatter `created_at`; use current time if missing | Inform only |
 
@@ -175,7 +175,7 @@ Version stamp rule: when creating or updating `task.md` frontmatter, read `.agen
 ## Notes
 
 1. **Issue validation**: verify that the Issue exists before continuing
-2. **Duplicate task**: if this Issue already has a linked task, ask the user before creating a new one
+2. **Duplicate task**: if this Issue already has a linked task, **reuse it by default** instead of creating a new one (do not ask the user)
 3. **Next step**: after import, run `analyze-task` before `plan-task`
 
 ## Error Handling

package/templates/.agents/skills/import-issue/SKILL.zh-CN.md

@@ -25,7 +25,7 @@ description: "从 Issue 导入并创建任务"
 ### 2. 检查已有任务
 
 2.1 搜索 `.agents/workspace/active/` 中是否已有链接到此 Issue 的任务。
-- 如果找到，询问用户是重新导入还是继续使用现有任务
+- 如果找到，**默认复用现有任务**（场景 A），不询问用户；在最终告知中明确「已复用现有任务 `{task-id}`，未重新导入」。若用户希望重新导入，需要先手动归档/删除已有任务再次执行本技能
 - 如果未找到，继续执行 2.2
 
 2.2 按 `.agents/rules/issue-pr-commands.md` 的“历史任务评论扫描”命令扫描 Issue 评论中的同步标记，查找可恢复的历史任务 ID。
@@ -44,7 +44,7 @@ description: "从 Issue 导入并创建任务"
 
 | 场景 | 触发条件 | task ID 来源 | created_at 来源 | 用户确认 |
 |---|---|---|---|---|
-| 场景 A | 2.1 命中本地任务 | 复用本地 ID | 本地保留 | 必须询问"重新导入还是继续使用现有任务" |
+| 场景 A | 2.1 命中本地任务 | 复用本地 ID | 本地保留 | 默认复用，不询问；告知用户已复用 |
 | 场景 B | 2.1 无命中 + 2.2 无候选 | `date +%Y%m%d-%H%M%S` 新建 | 当前时间 | 不需要 |
 | 场景 C | 2.1 无命中 + 2.2 有候选 | 自动复用最早候选 ID | 优先用远端 frontmatter 的 `created_at`，缺失时用当前时间 | 告知即可 |
 
@@ -175,7 +175,7 @@ Issue #{number} 已导入。
 ## 注意事项
 
 1. **Issue 验证**：在继续之前检查 Issue 是否存在
-2. **重复任务**：如果此 Issue 已有关联任务，在创建新任务前询问用户
+2. **重复任务**：如果此 Issue 已有关联任务，**默认复用**而非创建新任务（不询问用户）
 3. **下一步**：导入完成后，先执行 `analyze-task`，再进入 `plan-task`
 
 ## 错误处理

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

@@ -167,10 +167,10 @@ Output file:
 Important: human review checkpoint.
 Please review the technical plan before continuing to implementation.
 
-Next step - implement the task:
-  - Claude Code / OpenCode: /implement-task {task-id}
-  - Gemini CLI: /{{project}}:implement-task {task-id}
-  - Codex CLI: $implement-task {task-id}
+Next step - review the technical plan:
+  - Claude Code / OpenCode: /review-plan {task-id}
+  - Gemini CLI: /{{project}}:review-plan {task-id}
+  - Codex CLI: $review-plan {task-id}
 ```
 
 ## Completion Checklist

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

@@ -167,10 +167,10 @@ node .agents/scripts/validate-artifact.js gate plan-task .agents/workspace/activ
 重要：人工审查检查点。
 请在继续实现之前审查技术方案。
 
-下一步 - 实施任务：
-  - Claude Code / OpenCode：/implement-task {task-id}
-  - Gemini CLI：/agent-infra:implement-task {task-id}
-  - Codex CLI：$implement-task {task-id}
+下一步 - 审查技术方案：
+  - Claude Code / OpenCode：/review-plan {task-id}
+  - Gemini CLI：/{{project}}:review-plan {task-id}
+  - Codex CLI：$review-plan {task-id}
 ```
 
 ## 完成检查清单

package/templates/.agents/skills/restore-task/SKILL.en.md

@@ -43,10 +43,11 @@ Rules:
 - map `{file-stem}` back to filenames:
   - `task` -> `task.md`
   - `analysis` / `analysis-r{N}` -> matching `.md`
+  - `review-analysis` / `review-analysis-r{N}` -> matching `.md`
   - `plan` / `plan-r{N}` -> matching `.md`
-  - `implementation` / `implementation-r{N}` -> matching `.md`
-  - `review` / `review-r{N}` -> matching `.md`
-  - `refinement` / `refinement-r{N}` -> matching `.md`
+  - `review-plan` / `review-plan-r{N}` -> matching `.md`
+  - `code` / `code-r{N}` -> matching `.md`
+  - `review-code` / `review-code-r{N}` -> matching `.md`
 
 ### 4. Process Chunks and Check the Local Directory
 

package/templates/.agents/skills/restore-task/SKILL.zh-CN.md

@@ -43,10 +43,11 @@ description: "从平台 Issue 评论还原本地任务文件"
 - 将 `{file-stem}` 映射回文件名：
   - `task` -> `task.md`
   - `analysis` / `analysis-r{N}` -> 对应 `.md`
+  - `review-analysis` / `review-analysis-r{N}` -> 对应 `.md`
   - `plan` / `plan-r{N}` -> 对应 `.md`
-  - `implementation` / `implementation-r{N}` -> 对应 `.md`
-  - `review` / `review-r{N}` -> 对应 `.md`
-  - `refinement` / `refinement-r{N}` -> 对应 `.md`
+  - `review-plan` / `review-plan-r{N}` -> 对应 `.md`
+  - `code` / `code-r{N}` -> 对应 `.md`
+  - `review-code` / `review-code-r{N}` -> 对应 `.md`
 
 ### 4. 处理分片并检查本地目录
 

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

@@ -0,0 +1,76 @@
+---
+name: review-analysis
+description: "Review the requirement analysis artifact"
+---
+
+# Requirement Analysis Review
+
+Review the latest analysis artifact and produce `review-analysis.md` or `review-analysis-r{N}.md`.
+
+## Boundary / Critical Rules
+
+- This skill only reviews analysis 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
+```
+
+## Steps
+
+### 1. Verify Prerequisites
+
+Require `task.md` and at least one analysis artifact: `analysis.md` or `analysis-r{N}.md`.
+
+### 2. Determine Review Round
+
+Record `{analysis-artifact}`, `{review-round}`, and `{review-artifact}` (`review-analysis.md` or `review-analysis-r{N}.md`).
+
+### 3. Read Analysis Context
+
+Read `{analysis-artifact}`, `task.md`, and Issue context when available.
+
+### 4. Perform Review
+
+Check requirement completeness, risks, affected scope, open questions, and effort estimates.
+
+> 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 `requirement-analysis-review`, refresh task metadata, and append:
+`- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Analysis 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-analysis .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-analysis/SKILL.zh-CN.md

@@ -0,0 +1,102 @@
+---
+name: review-analysis
+description: "审查需求分析报告"
+---
+
+# 需求分析审查
+
+审查最新需求分析产物，并产出 `review-analysis.md` 或 `review-analysis-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
+```
+
+状态核对完成前，禁止任何关于外部状态的断言。
+
+## 执行步骤
+
+### 1. 验证前置条件
+
+要求存在：
+- `.agents/workspace/active/{task-id}/task.md`
+- 至少一个分析产物：`analysis.md` 或 `analysis-r{N}.md`
+
+### 2. 确定审查轮次
+
+扫描任务目录并记录：
+- `{analysis-artifact}`：最高轮次的分析产物
+- `{review-round}`
+- `{review-artifact}`：`review-analysis.md` 或 `review-analysis-r{N}.md`
+
+### 3. 阅读分析上下文
+
+读取最新 `{analysis-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`：requirement-analysis-review
+- `assigned_to`：{当前代理}
+- `updated_at`：{当前时间}
+- `agent_infra_version`：按 `.agents/rules/version-stamp.md` 取值
+- 追加：
+  `- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Analysis 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-analysis .agents/workspace/active/{task-id} {review-artifact} --format text
+```
+
+校验通过后继续告知用户；校验失败则修复报告或 task 状态后重跑。
+
+### 8. 告知用户
+
+按 `reference/output-templates.md` 的结论分支输出，并展示所有 TUI 的下一步命令。
+
+## 完成检查清单
+
+- [ ] 已审查最新分析上下文
+- [ ] 已创建 `{review-artifact}`
+- [ ] 已更新 task.md 并追加 Activity Log
+- [ ] 已展示所有 TUI 的下一步命令
+
+## 注意事项
+
+- 首轮审查使用 `review-analysis.md`，后续轮次使用 `review-analysis-r{N}.md`
+- 所有问题都要引用具体文件路径和行号；分析产物问题可引用 `{analysis-artifact}` 的行号

package/templates/.agents/skills/review-analysis/config/verify.en.json

@@ -0,0 +1,51 @@
+{
+  "skill": "review-analysis",
+  "checks": {
+    "task-meta": {
+      "required_fields": [
+        "id",
+        "type",
+        "workflow",
+        "status",
+        "created_at",
+        "updated_at",
+        "agent_infra_version",
+        "current_step",
+        "assigned_to"
+      ],
+      "expected_step": "requirement-analysis-review"
+    },
+    "artifact": {
+      "file_pattern": "review-analysis.md|review-analysis-r{N}.md",
+      "required_sections": [
+        "Review Summary",
+        "Findings",
+        "Environment-Blocked Findings",
+        "Conclusion and Recommendations",
+        "State Check",
+        "Evidence"
+      ],
+      "required_patterns": [
+        "^### Approval Decision$",
+        "^\\$ "
+      ],
+      "freshness_minutes": 30
+    },
+    "activity-log": {
+      "expected_action_pattern": "Analysis Review \\(Round \\d+\\)",
+      "freshness_minutes": 30
+    },
+    "platform-sync": {
+      "when": "issue_number_exists",
+      "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": "pendingDesignWork",
+      "expected_comment_marker_key": "artifact"
+    }
+  }
+}

package/templates/.agents/skills/review-analysis/config/verify.zh-CN.json

@@ -0,0 +1,51 @@
+{
+  "skill": "review-analysis",
+  "checks": {
+    "task-meta": {
+      "required_fields": [
+        "id",
+        "type",
+        "workflow",
+        "status",
+        "created_at",
+        "updated_at",
+        "agent_infra_version",
+        "current_step",
+        "assigned_to"
+      ],
+      "expected_step": "requirement-analysis-review"
+    },
+    "artifact": {
+      "file_pattern": "review-analysis.md|review-analysis-r{N}.md",
+      "required_sections": [
+        "审查摘要",
+        "问题清单",
+        "环境性遗留",
+        "结论与建议",
+        "状态核对",
+        "证据原文"
+      ],
+      "required_patterns": [
+        "^### 审查决定$",
+        "^\\$ "
+      ],
+      "freshness_minutes": 30
+    },
+    "activity-log": {
+      "expected_action_pattern": "Analysis Review \\(Round \\d+\\)",
+      "freshness_minutes": 30
+    },
+    "platform-sync": {
+      "when": "issue_number_exists",
+      "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": "pendingDesignWork",
+      "expected_comment_marker_key": "artifact"
+    }
+  }
+}

package/templates/.agents/skills/review-analysis/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 requirement analysis needs broad rewriting or fresh clarification, 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} requirement analysis 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 the 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 /analyze-task.
+```
+
+### Scenario B: Approved with findings
+
+```text
+Task {task-id} requirement analysis 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 analysis before continuing (recommended):
+  - Claude Code / OpenCode: /analyze-task {task-id}
+  - Gemini CLI: /agent-infra:analyze-task {task-id}
+  - Codex CLI: $analyze-task {task-id}
+
+Or proceed directly to planning:
+  - 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 /analyze-task.
+```
+
+### Scenario C: Changes requested
+
+```text
+Task {task-id} requirement analysis 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 requirement analysis:
+  - Claude Code / OpenCode: /analyze-task {task-id}
+  - Gemini CLI: /agent-infra:analyze-task {task-id}
+  - Codex CLI: $analyze-task {task-id}
+
+[When env-blocked > 0, append:]
+Reminder: env-blocked items belong in the PR description manual verification checklist and should not trigger /analyze-task.
+```
+
+### Scenario D: Rejected
+
+```text
+Task {task-id} requirement analysis review completed. Verdict: rejected, fresh analysis or requirement clarification 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 - re-analyze:
+  - Claude Code / OpenCode: /analyze-task {task-id}
+  - Gemini CLI: /agent-infra:analyze-task {task-id}
+  - Codex CLI: $analyze-task {task-id}
+
+[When env-blocked > 0, append:]
+Reminder: env-blocked items belong in the PR description manual verification checklist and should not trigger /analyze-task.
+```

package/templates/.agents/skills/review-analysis/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：/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 的「待人工验证」清单中承接，不应触发 /analyze-task。
+```
+
+### 场景 B：通过但有问题
+
+```text
+任务 {task-id} 需求分析审查完成。结论：通过。
+- 阻塞项：0 | 主要问题：{n} | 次要问题：{n}[ | 环境性遗留：{n}（不在 AI 修复范围）]
+- 审查报告：.agents/workspace/active/{task-id}/{review-artifact}
+
+下一步 - 修订分析后继续（推荐）：
+  - Claude Code / OpenCode：/analyze-task {task-id}
+  - Gemini CLI：/agent-infra:analyze-task {task-id}
+  - Codex CLI：$analyze-task {task-id}
+
+或直接进入方案设计：
+  - 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 的「待人工验证」清单中承接，不应触发 /analyze-task。
+```
+
+### 场景 C：需要修改
+
+```text
+任务 {task-id} 需求分析审查完成。结论：需要修改。
+- 阻塞项：{n} | 主要问题：{n} | 次要问题：{n}[ | 环境性遗留：{n}（不在 AI 修复范围）]
+- 审查报告：.agents/workspace/active/{task-id}/{review-artifact}
+
+下一步 - 修订需求分析：
+  - Claude Code / OpenCode：/analyze-task {task-id}
+  - Gemini CLI：/agent-infra:analyze-task {task-id}
+  - Codex CLI：$analyze-task {task-id}
+
+[当 env-blocked > 0 时，在最后附加一行：]
+提醒：env-blocked 项需在 PR description 的「待人工验证」清单中承接，不应触发 /analyze-task。
+```
+
+### 场景 D：拒绝
+
+```text
+任务 {task-id} 需求分析审查完成。结论：拒绝，需要重新分析或补充需求澄清。
+- 阻塞项：{n} | 主要问题：{n} | 次要问题：{n}[ | 环境性遗留：{n}（不在 AI 修复范围）]
+- 审查报告：.agents/workspace/active/{task-id}/{review-artifact}
+
+下一步 - 重新分析：
+  - Claude Code / OpenCode：/analyze-task {task-id}
+  - Gemini CLI：/agent-infra:analyze-task {task-id}
+  - Codex CLI：$analyze-task {task-id}
+
+[当 env-blocked > 0 时，在最后附加一行：]
+提醒：env-blocked 项需在 PR description 的「待人工验证」清单中承接，不应触发 /analyze-task。
+```

package/templates/.agents/skills/review-analysis/reference/report-template.en.md

@@ -0,0 +1,90 @@
+# Review Report Template
+
+Use this template when writing `review-analysis.md` or `review-analysis-r{N}.md`.
+
+## Output Template
+
+```markdown
+# Requirement Analysis Review Report
+
+- **Review Round**: Round {review-round}
+- **Artifact File**: `{review-artifact}`
+- **Review Input**:
+  - `{analysis-artifact}`
+
+## State Check
+
+> Paste the raw state-check command output; each command starts with `$ `.
+
+## Review Summary
+
+- **Reviewer**: {reviewer-name}
+- **Review Time**: {timestamp}
+- **Scope**: {file-count and major modules}
+- **Overall Verdict**: {Approved / Changes Requested / Rejected}
+- **Findings (AI-actionable)**: 0 blockers, 0 majors, 0 minors / **env-blocked**: 0
+
+## Findings
+
+### Blockers (must fix)
+
+#### 1. {Issue title}
+**File**: `{file-path}:{line-number}`
+**Description**: {details}
+**Suggested Fix**: {fix suggestion}
+
+### Major Issues (should fix)
+
+#### 1. {Issue title}
+**File**: `{file-path}:{line-number}`
+**Description**: {details}
+**Suggested Fix**: {fix suggestion}
+
+### Minor Issues (optional improvements)
+
+#### 1. {Improvement point}
+**File**: `{file-path}:{line-number}`
+**Suggestion**: {improvement suggestion}
+
+## Environment-Blocked Findings
+
+> Items the AI agent cannot close in the current execution environment; they do not participate in the next analysis round. Maintainers carry them in the PR description as a "manual verification required" checklist.
+
+#### 1. {environment-blocked finding title}
+**File**: `{file-path}:{line-number}` (if applicable)
+**Description**: {details}
+**Required Environment**: {e.g. Docker sandbox / macOS host / privileged root / third-party account}
+**Manual Verification Steps**: {steps for the human verifier}
+
+> If this round has no env-blocked findings, keep the section heading and write "None".
+
+
+## Evidence
+
+> Pair each "I verified X" claim with the corresponding raw tool output; the gate only checks that this section exists and at least one `$ ` line is present.
+
+- Claim: {verified claim}
+```text
+$ {command}
+{raw output}
+```
+
+## Highlights
+
+- {what went well}
+
+## Alignment with Plan
+
+- [ ] Implementation matches the technical plan
+- [ ] No unintended scope expansion
+
+## Conclusion and Recommendation
+
+### Approval Decision
+- [ ] Approved
+- [ ] Changes Requested
+- [ ] Rejected
+
+### Next Steps
+{recommended next step}
+```