@fitlab-ai/agent-infra 0.6.5 → 0.7.1

package/templates/.agents/scripts/validate-artifact.js

@@ -203,7 +203,7 @@ function runCheck(type, context) {
   }
 }
 
-// === Check Implementations ===
+// === Check Functions ===
 
 function checkTaskMeta({ taskDir, config }) {
   const task = loadTask(taskDir);

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

@@ -27,6 +27,10 @@ tail .agents/workspace/active/{task-id}/task.md
 
 Before the state check is complete, do not make external-state assertions such as "the code is unchanged", "tests passed", or "there are no other references", including in reasoning. This gate is only a structural floor; evidence pairing and authenticity still require the report template and review discipline.
 
+## 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
@@ -115,6 +119,18 @@ Create `.agents/workspace/active/{task-id}/{analysis-artifact}`.
 ## Dependencies
 - {Required dependencies and coordination with other modules}
 
+## Assumptions
+
+> If this analysis depends on assumptions, list them here; omit this section if there are none.
+
+- {assumption}
+
+## Open Questions
+
+> If there are unresolved questions for human review, list them here; omit this section if there are none.
+
+- {open question}
+
 ## Effort and Complexity Assessment
 - Complexity: {High/Medium/Low}
 - Risk level: {High/Medium/Low}
@@ -189,10 +205,10 @@ Summary:
 Output file:
 - Analysis report: .agents/workspace/active/{task-id}/{analysis-artifact}
 
-Next step - create technical plan:
-  - Claude Code / OpenCode: /plan-task {task-id}
-  - Gemini CLI: /{{project}}:plan-task {task-id}
-  - Codex CLI: $plan-task {task-id}
+Next step - review the analysis:
+  - Claude Code / OpenCode: /review-analysis {task-id}
+  - Gemini CLI: /{{project}}:review-analysis {task-id}
+  - Codex CLI: $review-analysis {task-id}
 ```
 
 ## Completion Checklist

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

@@ -27,8 +27,11 @@ tail .agents/workspace/active/{task-id}/task.md
 
 状态核对完成前，禁止任何关于外部状态的断言（例如“代码没变”“测试已通过”“没有其他引用”），包括思考阶段。本门禁只提供结构下限；逐条证据配对和真实性仍需按报告模板与审查要求核对。
 
-## 执行步骤
+## 任务入参短号别名
+
+> 如果 `{task-id}` 入参以 `#` 开头，先读取 `.agents/rules/task-short-id.md` 的「SKILL 入参解析」段执行解析；后续命令视 `{task-id}` 为解析后的全长 `TASK-YYYYMMDD-HHMMSS` 形式。
 
+## 执行步骤
 ### 1. 验证前置条件
 
 检查必要文件：
@@ -115,6 +118,18 @@ tail .agents/workspace/active/{task-id}/task.md
 ## 依赖关系
 - {需要的依赖和与其他模块的协调}
 
+## 假设
+
+> 如本次分析依赖某些假设，列在此处；没有则可省略本段。
+
+- {本轮分析所依赖的假设}
+
+## 未决问题
+
+> 如有需要人工裁定的未决问题，列在此处；没有则可省略本段。
+
+- {未决问题}
+
 ## 工作量和复杂度评估
 - 复杂度：{高/中/低}
 - 风险等级：{高/中/低}
@@ -189,10 +204,10 @@ node .agents/scripts/validate-artifact.js gate analyze-task .agents/workspace/ac
 产出文件：
 - 分析报告：.agents/workspace/active/{task-id}/{analysis-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：/review-analysis {task-id}
+  - Gemini CLI：/agent-infra:review-analysis {task-id}
+  - Codex CLI：$review-analysis {task-id}
 ```
 
 ## 完成检查清单

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

@@ -19,6 +19,10 @@ description: "Mark a task as blocked and record the reason"
 
 Version stamp rule: when creating or updating `task.md` frontmatter, read `.agents/rules/version-stamp.md` first and write or refresh `agent_infra_version`.
 
+## 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 Task Exists
@@ -79,6 +83,12 @@ If a valid `issue_number` exists, set `status: blocked` by following issue-sync.
 
 ### 7. Verification Gate
 
+**Release short id** (after the directory has already been moved; the script is idempotent and returns 0 even if the task isn't registered):
+
+```bash
+node .agents/scripts/task-short-id.js release "$task_id" || true
+```
+
 Run the verification gate to confirm the task artifact and sync state are valid:
 
 ```bash
@@ -116,6 +126,8 @@ Next step - check task status after unblocking:
   - Codex CLI: $check-task {task-id}
 ```
 
+
+
 ## Completion Checklist
 
 - [ ] Analyzed and documented the blocking reason

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

@@ -19,8 +19,11 @@ description: "标记任务为阻塞状态并记录原因"
 
 版本戳规则：创建或更新 `task.md` frontmatter 时，先读取 `.agents/rules/version-stamp.md`，并写入或刷新 `agent_infra_version`。
 
-## 执行步骤
+## 任务入参短号别名
+
+> 如果 `{task-id}` 入参以 `#` 开头，先读取 `.agents/rules/task-short-id.md` 的「SKILL 入参解析」段执行解析；后续命令视 `{task-id}` 为解析后的全长 `TASK-YYYYMMDD-HHMMSS` 形式。
 
+## 执行步骤
 ### 1. 验证任务存在
 
 检查任务是否存在于 `.agents/workspace/active/{task-id}/`。
@@ -79,6 +82,12 @@ ls .agents/workspace/blocked/{task-id}/task.md
 
 ### 7. 完成校验
 
+**释放短号**（先 `mv` 目录已成功，再 release；脚本幂等，未在注册表也返回 0）：
+
+```bash
+node .agents/scripts/task-short-id.js release "$task_id" || true
+```
+
 运行完成校验，确认任务产物和同步状态符合规范：
 
 ```bash
@@ -116,6 +125,8 @@ node .agents/scripts/validate-artifact.js gate block-task .agents/workspace/bloc
   - Codex CLI：$check-task {task-id}
 ```
 
+
+
 ## 完成检查清单
 
 - [ ] 分析并记录了阻塞原因

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

@@ -13,6 +13,10 @@ description: "Cancel an unneeded task and move it"
 
 Version stamp rule: when creating or updating `task.md` frontmatter, read `.agents/rules/version-stamp.md` first and write or refresh `agent_infra_version`.
 
+## 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 Task Exists
@@ -92,6 +96,12 @@ The cancellation comment must include at least:
 
 ### 7. Verification Gate
 
+**Release short id** (after the directory has already been moved; the script is idempotent and returns 0 even if the task isn't registered):
+
+```bash
+node .agents/scripts/task-short-id.js release "$task_id" || true
+```
+
 Run the verification gate to confirm the moved task and sync state are valid:
 
 ```bash
@@ -125,6 +135,8 @@ Next step - inspect the moved task:
   - Codex CLI: $check-task {task-id}
 ```
 
+
+
 ## Completion Checklist
 
 - [ ] Recorded the cancellation reason and updated task.md

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

@@ -13,8 +13,11 @@ description: "取消不再需要的任务并转移"
 
 版本戳规则：创建或更新 `task.md` frontmatter 时，先读取 `.agents/rules/version-stamp.md`，并写入或刷新 `agent_infra_version`。
 
-## 执行步骤
+## 任务入参短号别名
+
+> 如果 `{task-id}` 入参以 `#` 开头，先读取 `.agents/rules/task-short-id.md` 的「SKILL 入参解析」段执行解析；后续命令视 `{task-id}` 为解析后的全长 `TASK-YYYYMMDD-HHMMSS` 形式。
 
+## 执行步骤
 ### 1. 验证任务存在
 
 依次检查以下目录：
@@ -92,6 +95,12 @@ ls .agents/workspace/completed/{task-id}/task.md
 
 ### 7. 完成校验
 
+**释放短号**（先 `mv` 目录已成功，再 release；脚本幂等，未在注册表也返回 0）：
+
+```bash
+node .agents/scripts/task-short-id.js release "$task_id" || true
+```
+
 运行完成校验，确认任务转移和同步状态符合规范：
 
 ```bash
@@ -125,6 +134,8 @@ node .agents/scripts/validate-artifact.js gate cancel-task .agents/workspace/com
   - Codex CLI：$check-task {task-id}
 ```
 
+
+
 ## 完成检查清单
 
 - [ ] 已记录取消原因并更新 task.md

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

@@ -10,6 +10,10 @@ description: "Check a task's current status and progress"
 - This skill is **read-only** -- do not modify any files
 - Always check the active, blocked, and completed directories
 
+## 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. Locate Task
@@ -36,11 +40,12 @@ Extract from `task.md`:
 Scan and record the existence, round, and status of these artifact types:
 - `analysis.md`, `analysis-r{N}.md` - Requirement analysis
 - `plan.md`, `plan-r{N}.md` - Technical plan
-- `implementation.md`, `implementation-r2.md`, ... - Implementation reports
-- `refinement.md`, `refinement-r2.md`, ... - Refinement reports
-- `review.md`, `review-r2.md`, ... - Review reports
+- `code.md`, `code-r2.md`, ... - Code reports
+- `review-analysis.md`, `review-analysis-r{N}.md` - Requirement analysis review reports
+- `review-plan.md`, `review-plan-r{N}.md` - Technical plan review reports
+- `review-code.md`, `review-code-r{N}.md` - Code review reports
 
-For versioned artifacts (`analysis`, `plan`, `implementation`, `refinement`, `review`):
+For versioned artifacts (`analysis`, `review-analysis`, `plan`, `review-plan`, `code`, `review-code`):
 - Scan all versioned files of the same artifact type in the task directory
 - Record the latest round, latest file path, and total number of rounds for each artifact type
 - If the latest round is recorded in `task.md` Activity Log, cross-check it against the actual file when possible
@@ -64,28 +69,30 @@ Basic info:
 
 Workflow progress:
   [done]       Requirement Analysis  analysis-r2.md (Round 2, latest)
+  [done]       Analysis Review       review-analysis.md (Round 1, latest)
   [done]       Technical Design      plan.md (Round 1)
-  [current]    Implementation        implementation.md (Round 1)
-  [pending]    Refinement            refinement.md (Round 1 will be created next)
-  [pending]    Code Review           review.md (Round 1 will be created next)
+  [done]       Plan Review           review-plan.md (Round 1, latest)
+  [current]    Code                  code.md (Round 1)
+  [pending]    Code Review           review-code.md (Round 1 will be created next)
   [pending]    Final Commit
 
 Context files:
 - analysis.md:           Exists (Round 1)
 - analysis-r2.md:        Exists (Round 2, latest)
+- review-analysis.md:    Exists (Round 1, latest)
 - plan.md:               Exists (Round 1, latest)
-- implementation.md:     Exists (Round 1, latest)
-- refinement.md:         Not started
-- review.md:             Not started
+- review-plan.md:        Exists (Round 1, latest)
+- code.md:               Exists (Round 1, latest)
+- review-code.md:        Not started
 
 If multiple rounds exist, show all rounds and mark the latest, for example:
-- plan.md: Exists (Round 1)
-- plan-r2.md: Exists (Round 2, latest)
-- implementation.md: Exists (Round 1)
-- implementation-r2.md: Exists (Round 2, latest)
-- refinement.md: Exists (Round 1)
-- review.md: Exists (Round 1)
-- review-r2.md: Exists (Round 2, latest)
+- plan.md:             Exists (Round 1)
+- plan-r2.md:          Exists (Round 2, latest)
+- review-plan.md:      Exists (Round 1)
+- code.md:             Exists (Round 1)
+- code-r2.md:          Exists (Round 2, latest)
+- review-code.md:      Exists (Round 1)
+- review-code-r2.md:   Exists (Round 2, latest)
 
 Next step:
   Complete implementation, then run code review
@@ -107,26 +114,34 @@ Recommend the appropriate next skill based on the current workflow state. You mu
 > - `status = blocked` -> choose "Task Blocked"
 > - `status = completed` -> choose "Task Completed"
 > - `current_step = requirement-analysis` and the latest analysis artifact is complete -> choose "Analysis Complete"
+> - `current_step = requirement-analysis-review` and the latest analysis review artifact is approved -> choose "Analysis Review Passed"
+> - `current_step = requirement-analysis-review` and the latest analysis review artifact exists but is not approved or has findings -> choose "Analysis Review Has Issues"
 > - `current_step = technical-design` and the latest plan artifact is complete -> choose "Plan Complete"
-> - The latest implementation artifact exists and there is still no latest review artifact -> choose "Implementation Complete"
-> - The latest review artifact exists, the verdict is `Approved`, and `Blocker = 0`, `Major = 0`, `Minor = 0` -> choose "Review Passed"
-> - The latest review artifact exists, but any `Blocker`, `Major`, or `Minor` issue remains, or the verdict is not a clean approval -> choose "Review Has Issues"
+> - `current_step = technical-design-review` and the latest plan review artifact is approved -> choose "Plan Review Passed"
+> - `current_step = technical-design-review` and the latest plan review artifact exists but is not approved or has findings -> choose "Plan Review Has Issues"
+> - The latest code artifact exists and there is still no latest code review artifact -> choose "Code Complete"
+> - `current_step = code-review` and the latest code review artifact exists, the verdict is `Approved`, and `Blocker = 0`, `Major = 0`, `Minor = 0` -> choose "Code Review Passed"
+> - `current_step = code-review` and the latest code review artifact exists, but any `Blocker`, `Major`, or `Minor` issue remains, or the verdict is not a clean approval -> choose "Code Review Has Issues"
 >
-> **Important: if the latest review report contains any issue at all, do not use the "Review Passed" row. You must use "Review Has Issues" instead.**
-
-| Current State | Claude Code / OpenCode | Gemini CLI | Codex CLI |
-|--------------|------------------------|------------|-----------|
-| Analysis Complete | `/plan-task {task-id}` | `/{{project}}:plan-task {task-id}` | `$plan-task {task-id}` |
-| Plan Complete | `/implement-task {task-id}` | `/{{project}}:implement-task {task-id}` | `$implement-task {task-id}` |
-| Implementation Complete | `/review-task {task-id}` | `/{{project}}:review-task {task-id}` | `$review-task {task-id}` |
-| Review Passed | `/commit` | `/{{project}}:commit` | `$commit` |
-| Review Has Issues | `/refine-task {task-id}` | `/{{project}}:refine-task {task-id}` | `$refine-task {task-id}` |
-| Task Blocked | Unblock the task or provide the missing information | — | Unblock the task or provide the missing information |
-| Task Completed | No action needed | — | No action needed |
+> **Important: if the latest review report contains any issue at all, do not use the corresponding review-passed row. Use the corresponding has-issues row instead.**
+
+| Current State              | Claude Code / OpenCode                              | Gemini CLI                               | Codex CLI                                           |
+|----------------------------|-----------------------------------------------------|------------------------------------------|-----------------------------------------------------|
+| Analysis Complete          | `/review-analysis {task-id}`                        | `/{{project}}:review-analysis {task-id}` | `$review-analysis {task-id}`                        |
+| Analysis Review Passed     | `/plan-task {task-id}`                              | `/{{project}}:plan-task {task-id}`       | `$plan-task {task-id}`                              |
+| Analysis Review Has Issues | `/analyze-task {task-id}`                           | `/{{project}}:analyze-task {task-id}`    | `$analyze-task {task-id}`                           |
+| Plan Complete              | `/review-plan {task-id}`                            | `/{{project}}:review-plan {task-id}`     | `$review-plan {task-id}`                            |
+| Plan Review Passed         | `/code-task {task-id}`                              | `/{{project}}:code-task {task-id}`       | `$code-task {task-id}`                              |
+| Plan Review Has Issues     | `/plan-task {task-id}`                              | `/{{project}}:plan-task {task-id}`       | `$plan-task {task-id}`                              |
+| Code Complete              | `/review-code {task-id}`                            | `/{{project}}:review-code {task-id}`     | `$review-code {task-id}`                            |
+| Code Review Passed         | `/commit`                                           | `/{{project}}:commit`                    | `$commit`                                           |
+| Code Review Has Issues     | `/code-task {task-id}`                              | `/{{project}}:code-task {task-id}`       | `$code-task {task-id}`                              |
+| Task Blocked               | Unblock the task or provide the missing information | —                                        | Unblock the task or provide the missing information |
+| Task Completed             | No action needed                                    | —                                        | No action needed                                    |
 
 ## Notes
 
 1. **Read-only**: This skill only reads and reports -- it does not modify files
 2. **Multi-directory search**: Always check active, blocked, and completed
 3. **Quick reference**: Use this skill any time you need to see where a task is in the workflow
-4. **Versioned artifacts**: `analysis`, `plan`, `implementation`, `refinement`, and `review` must all report the actual round, not only the base filename
+4. **Versioned artifacts**: `analysis`, `review-analysis`, `plan`, `review-plan`, `code`, and `review-code` must all report the actual round, not only the base filename

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

@@ -10,8 +10,11 @@ description: "查看任务的当前状态和进度"
 - 本技能是**只读**操作 —— 不修改任何文件
 - 始终检查 active、blocked 和 completed 目录
 
-## 执行步骤
+## 任务入参短号别名
+
+> 如果 `{task-id}` 入参以 `#` 开头，先读取 `.agents/rules/task-short-id.md` 的「SKILL 入参解析」段执行解析；后续命令视 `{task-id}` 为解析后的全长 `TASK-YYYYMMDD-HHMMSS` 形式。
 
+## 执行步骤
 ### 1. 查找任务
 
 按以下优先顺序搜索任务：
@@ -36,11 +39,12 @@ description: "查看任务的当前状态和进度"
 按产物类型扫描并记录以下文件的存在、轮次和状态：
 - `analysis.md`、`analysis-r{N}.md` - 需求分析
 - `plan.md`、`plan-r{N}.md` - 技术方案
-- `implementation.md`、`implementation-r2.md`、... - 实现报告
-- `refinement.md`、`refinement-r2.md`、... - 修复报告
-- `review.md`、`review-r2.md`、... - 审查报告
+- `code.md`、`code-r2.md`、... - 实现报告
+- `review-analysis.md`、`review-analysis-r{N}.md` - 需求分析审查报告
+- `review-plan.md`、`review-plan-r{N}.md` - 技术方案审查报告
+- `review-code.md`、`review-code-r{N}.md` - 代码审查报告
 
-对于版本化产物（`analysis`、`plan`、`implementation`、`refinement`、`review`）：
+对于版本化产物（`analysis`、`review-analysis`、`plan`、`review-plan`、`code`、`review-code`）：
 - 扫描任务目录中的所有同类版本化文件
 - 记录每类产物的最新轮次、最新文件路径和总轮次数
 - 如果 `task.md` 的 Activity Log 记录了最新轮次，优先核对其与实际文件是否一致
@@ -64,28 +68,30 @@ description: "查看任务的当前状态和进度"
 
 工作流进度：
   [已完成]    需求分析        analysis-r2.md (Round 2, latest)
+  [已完成]    需求分析审查    review-analysis.md (Round 1, latest)
   [已完成]    技术设计        plan.md (Round 1)
-  [进行中]    实现            implementation.md (Round 1)
-  [待处理]    修复            refinement.md (Round 1 will be created next)
-  [待处理]    代码审查        review.md (Round 1 will be created next)
+  [已完成]    技术方案审查    review-plan.md (Round 1, latest)
+  [进行中]    实现            code.md (Round 1)
+  [待处理]    代码审查        review-code.md (Round 1 will be created next)
   [待处理]    最终提交
 
 上下文文件：
 - analysis.md：           已存在 (Round 1)
 - analysis-r2.md：        已存在 (Round 2, latest)
+- review-analysis.md：    已存在 (Round 1, latest)
 - plan.md：               已存在 (Round 1, latest)
-- implementation.md：     已存在 (Round 1, latest)
-- refinement.md：         未开始
-- review.md：             未开始
+- review-plan.md：        已存在 (Round 1, latest)
+- code.md：               已存在 (Round 1, latest)
+- review-code.md：        未开始
 
 如果存在多轮产物，显示所有轮次，并标记最新版本，例如：
-- plan.md：已存在 (Round 1)
-- plan-r2.md：已存在 (Round 2, latest)
-- implementation.md：已存在 (Round 1)
-- implementation-r2.md：已存在 (Round 2, latest)
-- refinement.md：已存在 (Round 1)
-- review.md：已存在 (Round 1)
-- review-r2.md：已存在 (Round 2, latest)
+- plan.md：             已存在 (Round 1)
+- plan-r2.md：          已存在 (Round 2, latest)
+- review-plan.md：      已存在 (Round 1)
+- code.md：             已存在 (Round 1)
+- code-r2.md：          已存在 (Round 2, latest)
+- review-code.md：      已存在 (Round 1)
+- review-code-r2.md：   已存在 (Round 2, latest)
 
 下一步：
   完成实现，然后执行代码审查
@@ -107,26 +113,34 @@ description: "查看任务的当前状态和进度"
 > - `status = blocked` → 选择「任务被阻塞」
 > - `status = completed` → 选择「任务已完成」
 > - `current_step = requirement-analysis` 且最新分析产物已完成 → 选择「分析完成」
+> - `current_step = requirement-analysis-review` 且最新需求分析审查产物通过 → 选择「需求分析审查通过」
+> - `current_step = requirement-analysis-review` 且最新需求分析审查产物存在但未通过或有问题 → 选择「需求分析审查有问题」
 > - `current_step = technical-design` 且最新计划产物已完成 → 选择「计划完成」
+> - `current_step = technical-design-review` 且最新技术方案审查产物通过 → 选择「技术方案审查通过」
+> - `current_step = technical-design-review` 且最新技术方案审查产物存在但未通过或有问题 → 选择「技术方案审查有问题」
 > - 最新实现产物已存在，且尚无最新审查产物 → 选择「实现完成」
-> - 最新审查产物存在，且结论为 `Approved`，同时 `Blocker = 0`、`Major = 0`、`Minor = 0` → 选择「审查通过」
-> - 最新审查产物存在，但仍有任何 `Blocker`、`Major` 或 `Minor` 问题，或结论不是无问题通过 → 选择「审查有问题」
+> - `current_step = code-review` 且最新代码审查产物存在，且结论为 `Approved`，同时 `Blocker = 0`、`Major = 0`、`Minor = 0` → 选择「代码审查通过」
+> - `current_step = code-review` 且最新代码审查产物存在，但仍有任何 `Blocker`、`Major` 或 `Minor` 问题，或结论不是无问题通过 → 选择「代码审查有问题」
 >
-> **特别注意：只要最新审查报告中存在任何问题，就不能使用「审查通过」行。必须改用「审查有问题」行。**
-
-| 当前状态 | Claude Code / OpenCode | Gemini CLI | Codex CLI |
-|---------|----------------------|------------|-----------|
-| 分析完成 | `/plan-task {task-id}` | `/agent-infra:plan-task {task-id}` | `$plan-task {task-id}` |
-| 计划完成 | `/implement-task {task-id}` | `/agent-infra:implement-task {task-id}` | `$implement-task {task-id}` |
-| 实现完成 | `/review-task {task-id}` | `/agent-infra:review-task {task-id}` | `$review-task {task-id}` |
-| 审查通过 | `/commit` | `/agent-infra:commit` | `$commit` |
-| 审查有问题 | `/refine-task {task-id}` | `/agent-infra:refine-task {task-id}` | `$refine-task {task-id}` |
-| 任务被阻塞 | 解除阻塞或提供所需信息 | — | 解除阻塞或提供所需信息 |
-| 任务已完成 | 无需操作 | — | 无需操作 |
+> **特别注意：只要最新审查报告中存在任何问题，就不能使用对应「审查通过」行。必须改用对应「审查有问题」行。**
+
+| 当前状态           | Claude Code / OpenCode       | Gemini CLI                               | Codex CLI                    |
+|--------------------|------------------------------|------------------------------------------|------------------------------|
+| 分析完成           | `/review-analysis {task-id}` | `/agent-infra:review-analysis {task-id}` | `$review-analysis {task-id}` |
+| 需求分析审查通过   | `/plan-task {task-id}`       | `/agent-infra:plan-task {task-id}`       | `$plan-task {task-id}`       |
+| 需求分析审查有问题 | `/analyze-task {task-id}`    | `/agent-infra:analyze-task {task-id}`    | `$analyze-task {task-id}`    |
+| 计划完成           | `/review-plan {task-id}`     | `/agent-infra:review-plan {task-id}`     | `$review-plan {task-id}`     |
+| 技术方案审查通过   | `/code-task {task-id}`       | `/agent-infra:code-task {task-id}`       | `$code-task {task-id}`       |
+| 技术方案审查有问题 | `/plan-task {task-id}`       | `/agent-infra:plan-task {task-id}`       | `$plan-task {task-id}`       |
+| 实现完成           | `/review-code {task-id}`     | `/agent-infra:review-code {task-id}`     | `$review-code {task-id}`     |
+| 代码审查通过       | `/commit`                    | `/agent-infra:commit`                    | `$commit`                    |
+| 代码审查有问题     | `/code-task {task-id}`       | `/agent-infra:code-task {task-id}`       | `$code-task {task-id}`       |
+| 任务被阻塞         | 解除阻塞或提供所需信息       | —                                        | 解除阻塞或提供所需信息       |
+| 任务已完成         | 无需操作                     | —                                        | 无需操作                     |
 
 ## 注意事项
 
 1. **只读**：本技能仅读取和报告 —— 不修改任何文件
 2. **多目录搜索**：始终检查 active、blocked 和 completed 目录
 3. **快速参考**：随时可以使用本技能检查任务在工作流中的位置
-4. **版本化产物**：`analysis`、`plan`、`implementation`、`refinement`、`review` 都需要报告实际轮次，而不是只报告固定文件名
+4. **版本化产物**：`analysis`、`review-analysis`、`plan`、`review-plan`、`code`、`review-code` 都需要报告实际轮次，而不是只报告固定文件名

package/templates/.agents/skills/close-codescan/SKILL.en.md

@@ -7,6 +7,10 @@ description: "Close a Code Scanning alert with a documented reason"
 
 Dismiss the specified Code Scanning (CodeQL) alert and record a justified reason.
 
+## 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.
+
 ## Execution Flow
 
 ### 1. Retrieve Alert Information
@@ -81,6 +85,11 @@ date "+%Y-%m-%d %H:%M:%S%:z"
   - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Alert Closed** by {agent} — Code Scanning alert #{alert-number} dismissed: {reason}
   ```
 - Archive the task
+- **Release short id** (after the archive `mv` succeeded; the script is idempotent):
+
+  ```bash
+  node .agents/scripts/task-short-id.js release "$task_id" || true
+  ```
 
 ### 8. Inform User
 
@@ -117,3 +126,5 @@ Next step - complete and archive the task if a related task exists:
 - Already closed: output "Alert #{number} is already {state}"
 - Permission error: output "No permission to modify alerts"
 - User canceled: output "Cancellation acknowledged"
+
+

package/templates/.agents/skills/close-codescan/SKILL.zh-CN.md

@@ -7,6 +7,10 @@ description: "关闭 Code Scanning 告警并记录理由"
 
 关闭指定的 Code Scanning（CodeQL）告警并记录合理的关闭理由。
 
+## 任务入参短号别名
+
+> 如果 `{task-id}` 入参以 `#` 开头，先读取 `.agents/rules/task-short-id.md` 的「SKILL 入参解析」段执行解析；后续命令视 `{task-id}` 为解析后的全长 `TASK-YYYYMMDD-HHMMSS` 形式。
+
 ## 执行流程
 
 ### 1. 获取告警信息
@@ -81,6 +85,11 @@ date "+%Y-%m-%d %H:%M:%S%:z"
   - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Alert Closed** by {agent} — Code Scanning alert #{alert-number} dismissed: {reason}
   ```
 - 归档任务
+- **释放短号**（归档目录已 mv 成功，再 release；脚本幂等）：
+
+  ```bash
+  node .agents/scripts/task-short-id.js release "$task_id" || true
+  ```
 
 ### 8. 告知用户
 
@@ -117,3 +126,5 @@ Code Scanning 告警 #{alert-number} 已关闭。
 - 已关闭：提示 "Alert #{number} is already {state}"
 - 权限错误：提示 "No permission to modify alerts"
 - 用户取消：提示 "Cancellation acknowledged"
+
+

package/templates/.agents/skills/close-dependabot/SKILL.en.md

@@ -7,6 +7,10 @@ description: "Close a Dependabot alert with a documented reason"
 
 Dismiss the specified Dependabot security alert and record a justified reason.
 
+## 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.
+
 ## Execution Flow
 
 ### 1. Retrieve Alert Information
@@ -89,6 +93,11 @@ date "+%Y-%m-%d %H:%M:%S%:z"
   - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Alert Closed** by {agent} — Dependabot alert #{alert-number} dismissed: {reason}
   ```
 - Archive the task
+- **Release short id** (after the archive `mv` succeeded; the script is idempotent):
+
+  ```bash
+  node .agents/scripts/task-short-id.js release "$task_id" || true
+  ```
 
 ### 8. Inform User
 
@@ -125,3 +134,5 @@ Next step - complete and archive the task if a related task exists:
 - Already closed: output "Alert #{number} is already {state}"
 - Permission error: output "No permission to modify alerts"
 - User canceled: output "Cancellation acknowledged"
+
+

package/templates/.agents/skills/close-dependabot/SKILL.zh-CN.md

@@ -7,6 +7,10 @@ description: "关闭 Dependabot 安全告警并记录理由"
 
 关闭指定的 Dependabot 安全告警并记录合理的关闭理由。
 
+## 任务入参短号别名
+
+> 如果 `{task-id}` 入参以 `#` 开头，先读取 `.agents/rules/task-short-id.md` 的「SKILL 入参解析」段执行解析；后续命令视 `{task-id}` 为解析后的全长 `TASK-YYYYMMDD-HHMMSS` 形式。
+
 ## 执行流程
 
 ### 1. 获取告警信息
@@ -89,6 +93,11 @@ date "+%Y-%m-%d %H:%M:%S%:z"
   - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Alert Closed** by {agent} — Dependabot alert #{alert-number} dismissed: {reason}
   ```
 - 归档任务
+- **释放短号**（归档目录已 mv 成功，再 release；脚本幂等）：
+
+  ```bash
+  node .agents/scripts/task-short-id.js release "$task_id" || true
+  ```
 
 ### 8. 告知用户
 
@@ -125,3 +134,5 @@ date "+%Y-%m-%d %H:%M:%S%:z"
 - 已关闭：提示 "Alert #{number} is already {state}"
 - 权限错误：提示 "No permission to modify alerts"
 - 用户取消：提示 "Cancellation acknowledged"
+
+