@fitlab-ai/agent-infra 0.6.5 → 0.7.0

package/templates/.agents/skills/{implement-task/reference/implementation-rules.en.md → code-task/reference/code-rules.en.md}

@@ -4,7 +4,7 @@ Read this file before coding or interpreting test failures.
 
 ## Execute Code Implementation
 
-Follow the `implementation` step in `.agents/workflows/feature-development.yaml`.
+Follow the `code` step in `.agents/workflows/feature-development.yaml`.
 
 **Required tasks**:
 - [ ] implement the feature code according to the plan
@@ -23,7 +23,7 @@ Follow the `implementation` step in `.agents/workflows/feature-development.yaml`
 
 During implementation:
 - **Inner loop**: after each change, run the project's **smoke subset** (see the `test` skill) for fast feedback
-- **Before writing the implementation report**: run the **core subset** as final verification so code entering review has passed the complete core checks
+- **Before writing the code report**: run the **core subset** as final verification so code entering review has passed the complete core checks
 
 > Refer to the `test` skill for project-specific commands; downstream projects without layered scripts should fall back to the full project test command.
 
@@ -39,8 +39,8 @@ Two-way failure handling:
    - continue until all required tests pass
 2. external blockers:
    - confirm the failure comes from missing environment, unrelated upstream breakage, or unclear requirements outside this task
-   - stop without creating `implementation.md` / `implementation-r{N}.md`
-   - do not mark implementation complete in `task.md`
+   - stop without creating `code.md` / `code-r{N}.md`
+   - do not mark code complete in `task.md`
    - do not output the normal success/next-step template
 
 ## Notes
@@ -49,5 +49,5 @@ Two-way failure handling:
 2. **No auto-commit**: do not run `git commit` or `git add`
 3. **Test quality**: new tests must validate meaningful business logic
 4. **Code quality**: follow project coding conventions
-5. **Plan deviation**: record any deviation in the implementation report
-6. **Versioning**: Round 1 uses `implementation.md`; later rounds use `implementation-r{N}.md`
+5. **Plan deviation**: record any deviation in the code report
+6. **Versioning**: Round 1 uses `code.md`; later rounds use `code-r{N}.md`

package/templates/.agents/skills/{implement-task/reference/implementation-rules.zh-CN.md → code-task/reference/code-rules.zh-CN.md}

@@ -4,7 +4,7 @@
 
 ## 执行代码实现
 
-遵循 `.agents/workflows/feature-development.yaml` 中的 `implementation` 步骤。
+遵循 `.agents/workflows/feature-development.yaml` 中的 `code` 步骤。
 
 **必做任务**：
 - [ ] 按计划实现功能代码
@@ -39,7 +39,7 @@
    - 持续处理直到所有必需测试通过
 2. 外部阻塞：
    - 确认失败来自缺失环境、无关的上游损坏，或任务范围外的需求不明确
-   - 停止，并且不要创建 `implementation.md` / `implementation-r{N}.md`
+   - 停止，并且不要创建 `code.md` / `code-r{N}.md`
    - 不要在 `task.md` 中把实现标记为完成
    - 不要输出正常的成功/下一步模板
 
@@ -50,4 +50,4 @@
 3. **测试质量**：新增测试必须验证有意义的业务逻辑
 4. **代码质量**：遵循项目编码规范
 5. **方案偏离**：任何偏离都要记录到实现报告中
-6. **版本命名**：Round 1 使用 `implementation.md`，后续轮次使用 `implementation-r{N}.md`
+6. **版本命名**：Round 1 使用 `code.md`，后续轮次使用 `code-r{N}.md`

package/templates/.agents/skills/code-task/reference/dual-mode.en.md

@@ -0,0 +1,69 @@
+# code-task dual mode
+
+This file documents `scripts/detect-mode.js`. The script is the source of truth; update this document whenever the script changes.
+
+## Input
+
+```bash
+node .agents/skills/code-task/scripts/detect-mode.js .agents/workspace/active/{task-id}
+```
+
+The script scans `plan.md` / `plan-r{N}.md`, `review-plan.md` / `review-plan-r{N}.md`, `code.md` / `code-r{N}.md`, and `review-code.md` / `review-code-r{N}.md` in the task directory.
+
+## Eight Branches
+
+> Branches are evaluated top-down in this table; the first match returns and skips later rows.
+
+| Condition | mode | exit | Behavior |
+|---|---|---:|---|
+| no code artifact | `init` | 0 | initial implementation, output `code.md` |
+| latest review-plan is approved (`Approved` or `Approved-with-issues`, i.e. `Overall Verdict: Approved` regardless of findings counts), its "Review Input" / "审查输入" entry names the same plan file as the latest `plan(-r{N})?.md` in the task directory, and its mtime is newer than the latest code artifact | `init` | 0 | plan has been approved after the latest code; enter a new implementation round, `next_round = code_max + 1`, `next_artifact = code-r{next_round}.md`. This branch fires regardless of whether review-code exists or passes. Plan and review-plan rounds are independent counters (e.g. `plan-r5` may be approved by `review-plan-r4`); the link is established via the review-plan's "Review Input" entry, not by matching round numbers. |
+| `rev_max < code_max` | `error` | 2 | latest code round is unreviewed; run `review-code` first |
+| `rev_max > code_max` | `error` | 2 | inconsistent state; manual inspection required |
+| latest review-code is Approved with 0/0/0 | `refused` | 1 | already approved; do not run `code-task` again |
+| latest review-code is Approved with major/minor findings | `fix` | 0 | optional fix mode |
+| latest review-code is Changes Requested | `fix` | 0 | required fix mode |
+| latest review-code is Rejected | `refused` | 1 | re-plan instead of local fixing |
+
+## Verdict Parsing
+
+The script supports zh-CN and English review-code reports:
+
+| Meaning | zh-CN | English |
+|---|---|---|
+| summary section | `## 审查摘要` | `## Review Summary` |
+| verdict field | `**总体结论**：` | `**Overall Verdict**:` |
+| findings field | `**发现（AI 可处理）**：` | `**Findings (AI-actionable)**:` |
+
+Verdict mapping:
+
+- `通过` / `Approved` -> `Approved`, then blocker/major/minor counts split it into `Approved` or `Approved-with-issues`
+- `需要修改` / `Changes Requested` -> `Changes Requested`
+- `拒绝` / `Rejected` -> `Rejected`
+
+env-blocked counts do not affect mode selection.
+
+## Output Contract
+
+The script prints JSON:
+
+```json
+{
+  "mode": "init",
+  "code_max": 0,
+  "rev_max": 0,
+  "verdict": null,
+  "next_round": 1,
+  "next_artifact": "code.md",
+  "review_artifact": null,
+  "message": "..."
+}
+```
+
+In the replan-driven init branch (row #2), `review_artifact` points to the `review-plan-r{N}.md` that triggered replan rather than a review-code artifact, preserving the attribution chain.
+
+exit code:
+
+- `0`: continue, `mode` is `init` or `fix`
+- `1`: stop, `mode` is `refused`
+- `2`: inconsistent state, `mode` is `error`

package/templates/.agents/skills/code-task/reference/dual-mode.zh-CN.md

@@ -0,0 +1,69 @@
+# code-task 双模式判定
+
+本文件说明 `scripts/detect-mode.js` 的行为。脚本是单点真相；修改脚本时必须同步更新本文档。
+
+## 输入
+
+```bash
+node .agents/skills/code-task/scripts/detect-mode.js .agents/workspace/active/{task-id}
+```
+
+脚本扫描任务目录中的 `plan.md` / `plan-r{N}.md`、`review-plan.md` / `review-plan-r{N}.md`、`code.md` / `code-r{N}.md` 和 `review-code.md` / `review-code-r{N}.md`。
+
+## 8 个分支
+
+> 分支按表中自上而下的顺序评估，命中即返回；后续分支不再判定。
+
+| 条件 | mode | exit | 行为 |
+|---|---|---:|---|
+| 无 code 产物 | `init` | 0 | 初次实现，产物为 `code.md` |
+| 最新 review-plan 已批准（`通过` 或 `通过 + major/minor 建议`，即 `Approved` 或 `Approved-with-issues`），且其「审查输入」/「Review Input」字段引用的 plan 文件 == 任务目录中最新的 `plan(-r{N})?.md`，且最新 review-plan 的 mtime > 最新 code 的 mtime | `init` | 0 | plan 已在 code 之后被批准；进入新一轮实现，`next_round = code_max + 1`、`next_artifact = code-r{next_round}.md`。**不论 review-code 是否已审**，本分支均先命中。plan 与 review-plan 的轮次独立递增（如 `plan-r5` 可被 `review-plan-r4` 批准），通过 review-plan 的「审查输入」字段建立批准关系，不要求同号 |
+| `rev_max < code_max` | `error` | 2 | 最新代码未审查，先运行 `review-code` |
+| `rev_max > code_max` | `error` | 2 | 数据状态异常，需要人工检查 |
+| 最新 review-code 为 Approved 且 0/0/0 | `refused` | 1 | 已通过，无需再次运行 `code-task` |
+| 最新 review-code 为 Approved 但有 major/minor | `fix` | 0 | 可选修复模式 |
+| 最新 review-code 为 Changes Requested | `fix` | 0 | 必需修复模式 |
+| 最新 review-code 为 Rejected | `refused` | 1 | 需要重新设计，不进入局部修复 |
+
+## verdict 解析
+
+脚本支持中文和英文 review-code 报告：
+
+| 语义 | 中文 | 英文 |
+|---|---|---|
+| 摘要段落 | `## 审查摘要` | `## Review Summary` |
+| 总体结论字段 | `**总体结论**：` | `**Overall Verdict**:` |
+| 发现统计字段 | `**发现（AI 可处理）**：` | `**Findings (AI-actionable)**:` |
+
+结论映射：
+
+- `通过` / `Approved` -> `Approved`，再按 blocker/major/minor 计数拆成 `Approved` 或 `Approved-with-issues`
+- `需要修改` / `Changes Requested` -> `Changes Requested`
+- `拒绝` / `Rejected` -> `Rejected`
+
+env-blocked 计数不参与 mode 判定。
+
+## 输出契约
+
+脚本输出 JSON：
+
+```json
+{
+  "mode": "init",
+  "code_max": 0,
+  "rev_max": 0,
+  "verdict": null,
+  "next_round": 1,
+  "next_artifact": "code.md",
+  "review_artifact": null,
+  "message": "..."
+}
+```
+
+`review_artifact` 字段在第 2 分支（replan-driven init）下指向触发的 `review-plan-r{N}.md` 而非 review-code 产物，用于追溯触发原因。
+
+exit code：
+
+- `0`：可继续，`mode` 为 `init` 或 `fix`
+- `1`：拒绝继续，`mode` 为 `refused`
+- `2`：状态异常，`mode` 为 `error`

package/templates/.agents/skills/{refine-task/reference/fix-workflow.en.md → code-task/reference/fix-mode.en.md}

@@ -1,6 +1,6 @@
 # Fix Workflow
 
-Read this file before changing code during refinement.
+Read this file before changing code during fix mode.
 
 ## Plan the Fixes
 
@@ -24,7 +24,7 @@ Detailed priority rules:
 
 env-blocked findings are outside the repair scope. Handling rules:
 - do not write code changes for these findings
-- list them unchanged in the refinement report's "Environment-Blocked Handling" section and mark them "outside AI repair scope"
+- list them unchanged in the code report's "Environment-Blocked Handling" section and mark them "outside AI repair scope"
 - do not repeat them under unresolved issues, to avoid visually double-counting them
 - their destination is the PR description, where maintainers carry them as a "manual verification required" checklist
 
@@ -38,7 +38,7 @@ For each fix:
 
 ## Run Test Verification
 
-Before writing the refinement report, run the project's **core subset** as final verification and confirm that all required tests still pass. If the project does not have layered scripts, fall back to the full project test command.
+Before writing the code report, run the project's **core subset** as final verification and confirm that all required tests still pass. If the project does not have layered scripts, fall back to the full project test command.
 
 ## Choose the Next-Step Branch
 
@@ -53,22 +53,22 @@ Prohibition:
 Required output template:
 
 ```text
-Task {task-id} refinement completed.
+Task {task-id} fix completed.
 
-Refinement status:
+Fix status:
 - Blockers fixed: {fixed-blockers}/{total-blockers}
 - Major issues fixed: {fixed-majors}/{total-majors}
 - Minor issues fixed: {fixed-minors}/{total-minors}
 - [If env-blocked > 0] env-blocked skipped: {count}
 - All tests passing: {yes/no}
 - Review input: {review-artifact}
-- Refinement artifact: {refinement-artifact}
+- Code artifact: {code-artifact}
 
 Next step - re-review or commit:
 - Re-review (always recommended):
-  - Claude Code / OpenCode: /review-task {task-id}
-  - Gemini CLI: /agent-infra:review-task {task-id}
-  - Codex CLI: $review-task {task-id}
+  - Claude Code / OpenCode: /review-code {task-id}
+  - Gemini CLI: /agent-infra:review-code {task-id}
+  - Codex CLI: $review-code {task-id}
 - Commit directly (optional; only when all issues are resolved and changes are low risk):
   - Claude Code / OpenCode: /commit
   - Gemini CLI: /agent-infra:commit
@@ -77,9 +77,9 @@ Next step - re-review or commit:
 
 ## Notes
 
-1. **Prerequisite**: a review artifact must exist (`review.md` or `review-r{N}.md`)
+1. **Prerequisite**: a code review artifact must exist (`review-code.md` or `review-code-r{N}.md`)
 2. **No auto-commit**: do not run `git commit`
 3. **Scope discipline**: only fix reviewed issues
 4. **Disagreement handling**: record any disagreement in the report
-5. **Re-review**: always recommend `review-task` as the default next step after refinement
-6. **Consistency**: the latest review artifact, Activity Log entry, and refinement report must reference the same round
+5. **Re-review**: always recommend `review-code` as the default next step after fix mode
+6. **Consistency**: the latest review artifact, Activity Log entry, and code report must reference the same round

package/templates/.agents/skills/{refine-task/reference/fix-workflow.zh-CN.md → code-task/reference/fix-mode.zh-CN.md}

@@ -24,7 +24,7 @@
 
 env-blocked 项不在修复范围。处理规则：
 - 不要为这些项编写代码改动
-- 在 refinement 报告的「环境性遗留处理」段落原样列出，标注「不在 AI 修复范围」
+- 在 code 报告的「环境性遗留处理」段落原样列出，标注「不在 AI 修复范围」
 - 不要在 unresolved 段落里重复列出（避免视觉计数翻倍）
 - 这些项的去向：维护者在 PR description 中以「待人工验证」清单承接
 
@@ -38,7 +38,7 @@ env-blocked 项不在修复范围。处理规则：
 
 ## 运行测试验证
 
-写 refinement 报告前，运行项目测试的 **core 子集**做最终验证，确保所有必需测试仍然通过。如果项目没有分层 script，回退到完整项目测试命令。
+写 code 报告前，运行项目测试的 **core 子集**做最终验证，确保所有必需测试仍然通过。如果项目没有分层 script，回退到完整项目测试命令。
 
 ## 选择下一步分支
 
@@ -62,13 +62,13 @@ env-blocked 项不在修复范围。处理规则：
 - [如 env-blocked > 0] 环境性遗留跳过：{数量}
 - 所有测试通过：{是/否}
 - 审查输入：{review-artifact}
-- 修复产物：{refinement-artifact}
+- 修复产物：{code-artifact}
 
 下一步 - 重新审查或提交：
 - 重新审查（始终推荐）：
-  - Claude Code / OpenCode：/review-task {task-id}
-  - Gemini CLI：/agent-infra:review-task {task-id}
-  - Codex CLI：$review-task {task-id}
+  - Claude Code / OpenCode：/review-code {task-id}
+  - Gemini CLI：/agent-infra:review-code {task-id}
+  - Codex CLI：$review-code {task-id}
 - 直接提交（可选；仅在所有问题已解决且风险可控时）：
   - Claude Code / OpenCode：/commit
   - Gemini CLI：/agent-infra:commit
@@ -77,9 +77,9 @@ env-blocked 项不在修复范围。处理规则：
 
 ## 注意事项
 
-1. **前置条件**：必须存在审查产物（`review.md` 或 `review-r{N}.md`）
+1. **前置条件**：必须存在代码审查产物（`review-code.md` 或 `review-code-r{N}.md`）
 2. **禁止自动提交**：不要执行 `git commit`
 3. **范围约束**：只修复审查中列出的问题
 4. **分歧处理**：如果不同意审查意见，要在报告里明确记录
-5. **重新审查**：修复后始终推荐执行 `review-task`
+5. **重新审查**：修复后始终推荐执行 `review-code`
 6. **一致性**：最新审查产物、Activity Log 记录和修复报告必须引用同一轮次

package/templates/.agents/skills/code-task/reference/output-template.en.md

@@ -0,0 +1,20 @@
+# Output Template
+
+When reporting that implementation is complete, use the following standard format:
+
+```text
+Task {task-id} code implementation complete.
+
+Summary:
+- Implementation round: Round {code-round}
+- Files modified: {count}
+- All tests passed: {yes/no}
+
+Output files:
+- Code report: .agents/workspace/active/{task-id}/{code-artifact}
+
+Next step - code review:
+  - Claude Code / OpenCode: /review-code {task-id}
+  - Gemini CLI: /{{project}}:review-code {task-id}
+  - Codex CLI: $review-code {task-id}
+```

package/templates/.agents/skills/code-task/reference/output-template.zh-CN.md

@@ -0,0 +1,20 @@
+# 输出模板
+
+向用户汇报实现完成时，使用以下标准格式：
+
+```text
+任务 {task-id} 实现完成。
+
+摘要：
+- 实现轮次：Round {code-round}
+- 修改文件：{数量}
+- 所有测试通过：{是/否}
+
+产出文件：
+- 实现报告：.agents/workspace/active/{task-id}/{code-artifact}
+
+下一步 - 代码审查：
+  - Claude Code / OpenCode：/review-code {task-id}
+  - Gemini CLI：/agent-infra:review-code {task-id}
+  - Codex CLI：$review-code {task-id}
+```

package/templates/.agents/skills/{implement-task → code-task}/reference/report-template.en.md

@@ -1,14 +1,14 @@
-# Implementation Report Template
+# Code Report Template
 
-Use this structure when creating `implementation.md` or `implementation-r{N}.md`.
+Use this structure when creating `code.md` or `code-r{N}.md`.
 
 ## Output Template
 
 ```markdown
 # Implementation Report
 
-- **Implementation Round**: Round {implementation-round}
-- **Artifact File**: `{implementation-artifact}`
+- **Implementation Round**: Round {code-round}
+- **Artifact File**: `{code-artifact}`
 
 ## State Check
 

package/templates/.agents/skills/{implement-task → code-task}/reference/report-template.zh-CN.md

@@ -1,14 +1,14 @@
 # 实现报告模板
 
-创建 `implementation.md` 或 `implementation-r{N}.md` 时，使用以下结构。
+创建 `code.md` 或 `code-r{N}.md` 时，使用以下结构。
 
 ## 输出模板
 
 ```markdown
 # 实现报告
 
-- **实现轮次**: Round {implementation-round}
-- **产物文件**: `{implementation-artifact}`
+- **实现轮次**: Round {code-round}
+- **产物文件**: `{code-artifact}`
 
 ## 状态核对