@fitlab-ai/agent-infra 0.6.5 → 0.7.1

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

@@ -26,6 +26,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 Task Exists
@@ -40,9 +44,11 @@ If not found in `active/`, check `blocked/` and `completed/`:
 
 ### 2. Verify Completion Prerequisites (Failure Must Stop)
 
+**Gate read (project-level PR flow policy)**: Before running this step, read `.agents/.airc.json`'s `requiresPullRequest` field. Treat missing or `true` as "PR flow enabled" (default); treat explicit `false` as "PR flow disabled". The completion check below is pruned accordingly.
+
 Before marking complete, verify ALL of these:
-- [ ] All workflow steps are complete (check workflow progress in task.md)
-- [ ] Code has been reviewed (`review.md` or `review-r{N}.md` exists, and the latest review verdict is Approved; or review was done externally)
+- [ ] All workflow steps are complete (check workflow progress in task.md; **for the `pr_tasks` list under each yaml `commit` step, count those items toward the missing-work decision only when `.agents/.airc.json:requiresPullRequest !== false`**)
+- [ ] Code has been reviewed (`review-code.md` or `review-code-r{N}.md` exists, and the latest review verdict is Approved; or review was done externally)
 - [ ] Code has been committed (no uncommitted changes related to this task)
 - [ ] Tests are passing
 
@@ -109,7 +115,7 @@ Check whether `task.md` includes a valid `issue_number`. If not, skip this step
 > Issue sync rules live in `.agents/rules/issue-sync.md`. Read that file before syncing, and complete upstream repository detection plus permission detection.
 
 If a valid `issue_number` exists:
-- First scan and backfill unpublished `task.md`, `analysis*.md`, `plan*.md`, `implementation*.md`, `review*.md`, and `refinement*.md` comments using the backfill rules in `.agents/rules/issue-sync.md` (`task.md` uses the idempotent update path)
+- First scan and backfill unpublished `task.md`, `analysis*.md`, `review-analysis*.md`, `plan*.md`, `review-plan*.md`, `code*.md`, and `review-code*.md` comments using the backfill rules in `.agents/rules/issue-sync.md` (`task.md` uses the idempotent update path)
 - Backfill checked `## Requirements` items to the Issue body by following the requirements-checkbox sync steps in issue-sync.md
 - Do not set any `status:` label — status labels are automatically cleared when the Issue is closed
 - Finally create or update the summary comment marked with the summary marker defined in `.agents/rules/issue-sync.md`
@@ -117,6 +123,12 @@ If a valid `issue_number` exists:
 
 ### 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
@@ -147,6 +159,8 @@ Deliverables:
 - {List of key outputs: files modified, tests added, etc.}
 ```
 
+
+
 ## Completion Checklist
 
 - [ ] Verified all workflow steps are complete

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

@@ -26,8 +26,11 @@ 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}/`。
@@ -40,9 +43,11 @@ tail .agents/workspace/active/{task-id}/task.md
 
 ### 2. 验证完成前置条件（未满足则必须停止）
 
+**门控读取（项目级 PR 流程策略）**：在执行本步骤前，读取 `.agents/.airc.json` 的 `requiresPullRequest` 字段；当字段缺失或为 `true` 时视为「启用 PR 流程」（默认），仅当显式为 `false` 时视为「关闭 PR 流程」。下面的工作流步骤完成判定按此规则裁剪。
+
 标记完成之前，验证以下所有条件：
-- [ ] 所有工作流步骤已完成（检查 task.md 中的工作流进度）
-- [ ] 代码已审查（`review.md` 或 `review-r{N}.md` 存在，且最新审查结论为 Approved；或已在外部完成审查）
+- [ ] 所有工作流步骤已完成（检查 task.md 中的工作流进度；**对 yaml 中 commit 步骤的 `pr_tasks` 列表，仅在 `.agents/.airc.json:requiresPullRequest !== false` 时计入未完成判定**）
+- [ ] 代码已审查（`review-code.md` 或 `review-code-r{N}.md` 存在，且最新审查结论为 Approved；或已在外部完成审查）
 - [ ] 代码已提交（没有与此任务相关的未提交变更）
 - [ ] 测试通过
 
@@ -109,7 +114,7 @@ ls .agents/workspace/completed/{task-id}/task.md
 > Issue 同步规则见 `.agents/rules/issue-sync.md`。执行同步前先读取该文件，完成 upstream 仓库检测和权限检测。
 
 如果存在有效的 `issue_number`：
-- 先按 `.agents/rules/issue-sync.md` 的补发规则扫描并补发未发布的 `task.md`、`analysis*.md`、`plan*.md`、`implementation*.md`、`review*.md`、`refinement*.md` 评论（`task.md` 走幂等更新路径）
+- 先按 `.agents/rules/issue-sync.md` 的补发规则扫描并补发未发布的 `task.md`、`analysis*.md`、`review-analysis*.md`、`plan*.md`、`review-plan*.md`、`code*.md`、`review-code*.md` 评论（`task.md` 走幂等更新路径）
 - 按 issue-sync.md 的需求复选框同步步骤，兜底同步 `## 需求` 中已勾选的条目到 Issue body
 - 不要设置 `status:` label — Issue 关闭后 status label 会被自动清除
 - 最后创建或更新 `.agents/rules/issue-sync.md` 中定义的 summary 评论标记对应的 summary 评论
@@ -117,6 +122,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
@@ -147,6 +158,8 @@ node .agents/scripts/validate-artifact.js gate complete-task .agents/workspace/c
 - {关键产出列表：修改的文件、添加的测试等}
 ```
 
+
+
 ## 完成检查清单
 
 - [ ] 验证了所有工作流步骤已完成

package/templates/.agents/skills/create-pr/SKILL.en.md

@@ -11,8 +11,28 @@ Create a Pull Request and, when task-related, sync the essential metadata and re
 
 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.
+
 ## Execution Flow
 
+### Pre-gate: Project-level PR Flow Check
+
+**Gate read (project-level PR flow policy)**: Before running any numbered step, read `.agents/.airc.json`'s `requiresPullRequest` field. Treat missing or `true` as "PR flow enabled" (default); treat explicit `false` as "PR flow disabled".
+
+Branch on the result:
+- missing / `true` -> continue to Step 1 below
+- explicit `false` -> output the message below and **stop immediately**. Do not run any subsequent numbered step, do not trigger any PR-creation command, do not modify `pr_number` in `task.md`, and do not publish a PR summary comment:
+
+```
+This project does not enable the PR flow (`.agents/.airc.json` sets `requiresPullRequest: false`).
+No Pull Request is required; run instead:
+  - Claude Code / OpenCode: /complete-task {task-id}
+  - Gemini CLI: /agent-infra:complete-task {task-id}
+  - Codex CLI: $complete-task {task-id}
+```
+
 ### 1. Parse Command Arguments
 
 Identify arguments from the command input:
@@ -57,7 +77,7 @@ For PRs where `{task-id}` is available, sync the core metadata immediately:
 
 ### 7. Publish the Review Summary
 
-Read the latest context artifacts when they exist: `plan.md` / `plan-r{N}.md`, `implementation.md` / `implementation-r{N}.md`, `review.md` / `review-r{N}.md`, and `refinement.md` / `refinement-r{N}.md`.
+Read the latest context artifacts when they exist: `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`.
 
 Aggregate a reviewer-facing summary from those artifacts and maintain a single idempotent summary comment via the hidden marker.
 

package/templates/.agents/skills/create-pr/SKILL.zh-CN.md

@@ -11,8 +11,28 @@ description: "创建 Pull Request 到目标分支"
 
 版本戳规则：创建或更新 `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` 形式。
+
 ## 执行流程
 
+### 前置门控：项目级 PR 流程检查
+
+**门控读取（项目级 PR 流程策略）**：在执行编号步骤前，读取 `.agents/.airc.json` 的 `requiresPullRequest` 字段；当字段缺失或为 `true` 时视为「启用 PR 流程」（默认），仅当显式为 `false` 时视为「关闭 PR 流程」。
+
+按读取结果分支：
+- 缺失 / `true` → 继续到下方第 1 步
+- 显式 `false` → 输出以下消息后**立即停止**，不要执行任何后续编号步骤、不要触发任何 PR 创建命令、不要修改 `task.md` 的 `pr_number`、不要发布 PR 摘要评论：
+
+```
+当前项目未启用 PR 流程（`.agents/.airc.json` 中 `requiresPullRequest: false`）。
+无需创建 Pull Request，请直接运行：
+  - Claude Code / OpenCode：/complete-task {task-id}
+  - Gemini CLI：/agent-infra:complete-task {task-id}
+  - Codex CLI：$complete-task {task-id}
+```
+
 ### 1. 解析命令参数
 
 从命令参数中识别：
@@ -57,7 +77,7 @@ description: "创建 Pull Request 到目标分支"
 
 ### 7. 发布审查摘要
 
-读取最新的上下文产物：`plan.md` / `plan-r{N}.md`、`implementation.md` / `implementation-r{N}.md`、`review.md` / `review-r{N}.md`、`refinement.md` / `refinement-r{N}.md`（存在时）。
+读取最新的上下文产物：`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`（存在时）。
 
 基于这些产物聚合 reviewer 摘要，并使用隐藏标记维护唯一且幂等的摘要评论。
 

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

@@ -22,6 +22,10 @@ After executing this skill, you **must** immediately update task status in task.
 
 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. Parse the User Description
@@ -126,6 +130,14 @@ Handle the result:
 
 ### 5. Verification Gate
 
+**Allocate short id first** (writes `short_id` back to task.md and the registry entry; the validation gate will read it):
+
+```bash
+node .agents/scripts/task-short-id.js alloc "$task_id"
+```
+
+If this fails (non-zero exit), follow the message — archive some active tasks or raise `task.shortIdLength` — and do NOT continue.
+
 Run the verification gate to confirm the task artifact and sync state are valid:
 
 ```bash
@@ -210,6 +222,8 @@ Next step - run requirements analysis:
 For later platform sync: after fixing auth / network / template issues, manually run the Issue creation flow in `.agents/rules/create-issue.md` for this task; or manually create/find an Issue and write `issue_number` into task.md so later skills can take over cascade sync.
 ```
 
+
+
 ## Completion Checklist
 
 - [ ] Created the task file `.agents/workspace/active/{task-id}/task.md`

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

@@ -22,8 +22,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. 解析用户描述
 
 从自然语言描述中提取：
@@ -126,6 +129,14 @@ date "+%Y-%m-%d %H:%M:%S%:z"
 
 ### 5. 完成校验
 
+**先调用短号分配**（保证 `short_id` 写回 task.md + 注册表 entry 已在；完成校验阶段会读取）：
+
+```bash
+node .agents/scripts/task-short-id.js alloc "$task_id"
+```
+
+如失败（退出码非 0），按提示「归档若干任务」或「调高 task.shortIdLength」处理；不要继续执行后续步骤。
+
 运行完成校验，确认任务产物和同步状态符合规范：
 
 ```bash
@@ -210,6 +221,8 @@ Issue 创建失败：
 后续如需平台同步：修复认证/网络/模板问题后，可按 `.agents/rules/create-issue.md` 对当前任务手动执行一次 Issue 创建；或手动创建/查找 Issue，并把 `issue_number` 写入 task.md，后续技能会接管级联同步。
 ```
 
+
+
 ## 完成检查清单
 
 - [ ] 创建了任务文件 `.agents/workspace/active/{task-id}/task.md`

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

@@ -13,6 +13,10 @@ Import the specified Code Scanning (CodeQL) alert and create a remediation task.
 - Do NOT auto-commit. Never execute `git commit` or `git add` automatically
 - After executing this skill, you **must** immediately update task status in 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.
+
 ## Execution Flow
 
 ### 1. Retrieve Alert Information
@@ -58,6 +62,14 @@ Update task.md: `current_step` -> `requirement-analysis`.
 
 ### 4. Verification Gate
 
+**Allocate short id first** (writes `short_id` back to task.md and the registry entry; the validation gate will read it):
+
+```bash
+node .agents/scripts/task-short-id.js alloc "$task_id"
+```
+
+If this fails (non-zero exit), follow the message — archive some active tasks or raise `task.shortIdLength` — and do NOT continue.
+
 Run the verification gate to confirm the task artifact and sync state are valid:
 
 ```bash
@@ -94,6 +106,8 @@ Next step:
   - Codex CLI: $analyze-task {task-id}
 ```
 
+
+
 ## Completion Checklist
 
 - [ ] Retrieved and recorded the key alert information
@@ -106,5 +120,5 @@ Next step:
 ## Error Handling
 
 - Alert not found: output "Code Scanning alert #{number} not found"
-- Alert already closed: ask the user whether to continue with analysis
+- Alert already closed: **proceed with task creation/reuse by default** and surface the alert's current state (dismissed/fixed) in the final notice; the user may archive the task manually if desired
 - Network/permission error: output the corresponding error information

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

@@ -13,6 +13,10 @@ description: "导入 Code Scanning 告警并创建修复任务"
 - 不要自动提交。绝不自动执行 `git commit` 或 `git add`
 - 执行本技能后，你**必须**立即更新 task.md 中的任务状态
 
+## 任务入参短号别名
+
+> 如果 `{task-id}` 入参以 `#` 开头，先读取 `.agents/rules/task-short-id.md` 的「SKILL 入参解析」段执行解析；后续命令视 `{task-id}` 为解析后的全长 `TASK-YYYYMMDD-HHMMSS` 形式。
+
 ## 执行流程
 
 ### 1. 获取告警信息
@@ -58,6 +62,14 @@ date "+%Y-%m-%d %H:%M:%S%:z"
 
 ### 4. 完成校验
 
+**先调用短号分配**（保证 `short_id` 写回 task.md + 注册表 entry 已在；完成校验阶段会读取）：
+
+```bash
+node .agents/scripts/task-short-id.js alloc "$task_id"
+```
+
+如失败（退出码非 0），按提示「归档若干任务」或「调高 task.shortIdLength」处理；不要继续执行后续步骤。
+
 运行完成校验，确认任务产物和同步状态符合规范：
 
 ```bash
@@ -94,6 +106,8 @@ Code Scanning 告警 #{alert-number} 已导入。
   - Codex CLI：$analyze-task {task-id}
 ```
 
+
+
 ## 完成检查清单
 
 - [ ] 获取并记录了告警关键信息
@@ -106,5 +120,5 @@ Code Scanning 告警 #{alert-number} 已导入。
 ## 错误处理
 
 - 告警未找到：提示 "Code Scanning alert #{number} not found"
-- 告警已关闭：询问用户是否继续分析
+- 告警已关闭：**默认仍继续创建/复用任务**，并在告知用户中明确该告警当前状态（dismissed/fixed）；用户可视情况手动归档任务
 - 网络/权限错误：提示相应信息

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

@@ -13,6 +13,10 @@ Import the specified Dependabot security alert and create a remediation task.
 - Do NOT auto-commit. Never execute `git commit` or `git add` automatically
 - After executing this skill, you **must** immediately update task status in 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.
+
 ## Execution Flow
 
 ### 1. Retrieve Alert Information
@@ -29,7 +33,7 @@ Extract key information:
 ### 2. Create the Task Directory and File
 
 Check whether `.agents/workspace/active/` already has a task for this alert.
-- If found, ask the user whether to re-import
+- If found, **reuse the existing task by default**; 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
 - If not found, create a new task
 
 Create directory: `.agents/workspace/active/TASK-{yyyyMMdd-HHmmss}/`
@@ -59,6 +63,14 @@ Update task.md: `current_step` -> `requirement-analysis`.
 
 ### 4. Verification Gate
 
+**Allocate short id first** (writes `short_id` back to task.md and the registry entry; the validation gate will read it):
+
+```bash
+node .agents/scripts/task-short-id.js alloc "$task_id"
+```
+
+If this fails (non-zero exit), follow the message — archive some active tasks or raise `task.shortIdLength` — and do NOT continue.
+
 Run the verification gate to confirm the task artifact and sync state are valid:
 
 ```bash
@@ -98,6 +110,8 @@ Next step:
   - Codex CLI: $analyze-task {task-id}
 ```
 
+
+
 ## Completion Checklist
 
 - [ ] Retrieved and recorded the key alert information
@@ -110,5 +124,5 @@ Next step:
 ## Error Handling
 
 - Alert not found: output "Security alert #{number} not found"
-- Alert already closed: ask the user whether to continue with analysis
+- Alert already closed: **proceed with task creation/reuse by default** and surface the alert's current state (dismissed/fixed) in the final notice; the user may archive the task manually if desired
 - Network/permission error: output the corresponding error information

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

@@ -13,6 +13,10 @@ description: "导入 Dependabot 安全告警并创建修复任务"
 - 不要自动提交。绝不自动执行 `git commit` 或 `git add`
 - 执行本技能后，你**必须**立即更新 task.md 中的任务状态
 
+## 任务入参短号别名
+
+> 如果 `{task-id}` 入参以 `#` 开头，先读取 `.agents/rules/task-short-id.md` 的「SKILL 入参解析」段执行解析；后续命令视 `{task-id}` 为解析后的全长 `TASK-YYYYMMDD-HHMMSS` 形式。
+
 ## 执行流程
 
 ### 1. 获取告警信息
@@ -29,7 +33,7 @@ description: "导入 Dependabot 安全告警并创建修复任务"
 ### 2. 创建任务目录和文件
 
 检查 `.agents/workspace/active/` 中是否已存在该告警的任务。
-- 如果找到，询问用户是否重新导入
+- 如果找到，**默认复用现有任务**，不询问用户；在最终告知中明确「已复用现有任务 `{task-id}`，未重新导入」。如需重新导入，需先归档/删除已有任务
 - 如果未找到，创建新任务
 
 创建目录：`.agents/workspace/active/TASK-{yyyyMMdd-HHmmss}/`
@@ -59,6 +63,14 @@ date "+%Y-%m-%d %H:%M:%S%:z"
 
 ### 4. 完成校验
 
+**先调用短号分配**（保证 `short_id` 写回 task.md + 注册表 entry 已在；完成校验阶段会读取）：
+
+```bash
+node .agents/scripts/task-short-id.js alloc "$task_id"
+```
+
+如失败（退出码非 0），按提示「归档若干任务」或「调高 task.shortIdLength」处理；不要继续执行后续步骤。
+
 运行完成校验，确认任务产物和同步状态符合规范：
 
 ```bash
@@ -98,6 +110,8 @@ node .agents/scripts/validate-artifact.js gate import-dependabot .agents/workspa
   - Codex CLI：$analyze-task {task-id}
 ```
 
+
+
 ## 完成检查清单
 
 - [ ] 获取并记录了告警关键信息
@@ -110,5 +124,5 @@ node .agents/scripts/validate-artifact.js gate import-dependabot .agents/workspa
 ## 错误处理
 
 - 告警未找到：提示 "Security alert #{number} not found"
-- 告警已关闭：询问用户是否继续分析
+- 告警已关闭：**默认仍继续创建/复用任务**，并在告知用户中明确该告警当前状态（dismissed/fixed）；用户可视情况手动归档任务
 - 网络/权限错误：提示相应信息

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

@@ -13,6 +13,10 @@ Import the specified Issue and create a task. Argument: issue number.
 - Do not write or modify business code; import only
 - After executing this skill, you **must** immediately update task status
 
+## 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 Issue Information
@@ -25,7 +29,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 +48,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 |
 
@@ -119,6 +123,14 @@ If task.md contains a valid `issue_number`, perform these sync actions (skip and
 
 ### 7. Verification Gate
 
+**Allocate short id first** (writes `short_id` back to task.md and the registry entry; the validation gate will read it):
+
+```bash
+node .agents/scripts/task-short-id.js alloc "$task_id"
+```
+
+If this fails (non-zero exit), follow the message — archive some active tasks or raise `task.shortIdLength` — and do NOT continue.
+
 Run the verification gate to confirm the task artifact and sync state are valid:
 
 ```bash
@@ -155,6 +167,8 @@ Next step - run requirements analysis:
   - Codex CLI: $analyze-task {task-id}
 ```
 
+
+
 ## Completion Checklist
 
 - [ ] Created the task file `.agents/workspace/active/{task-id}/task.md`
@@ -175,7 +189,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

@@ -13,6 +13,10 @@ description: "从 Issue 导入并创建任务"
 - 不要编写或修改业务代码。仅做导入
 - 执行本技能后，你**必须**立即更新任务状态
 
+## 任务入参短号别名
+
+> 如果 `{task-id}` 入参以 `#` 开头，先读取 `.agents/rules/task-short-id.md` 的「SKILL 入参解析」段执行解析；后续命令视 `{task-id}` 为解析后的全长 `TASK-YYYYMMDD-HHMMSS` 形式。
+
 ## 执行流程
 
 ### 1. 获取 Issue 信息
@@ -25,7 +29,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 +48,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`，缺失时用当前时间 | 告知即可 |
 
@@ -119,6 +123,14 @@ date "+%Y-%m-%d %H:%M:%S%:z"
 
 ### 7. 完成校验
 
+**先调用短号分配**（保证 `short_id` 写回 task.md + 注册表 entry 已在；完成校验阶段会读取）：
+
+```bash
+node .agents/scripts/task-short-id.js alloc "$task_id"
+```
+
+如失败（退出码非 0），按提示「归档若干任务」或「调高 task.shortIdLength」处理；不要继续执行后续步骤。
+
 运行完成校验，确认任务产物和同步状态符合规范：
 
 ```bash
@@ -155,6 +167,8 @@ Issue #{number} 已导入。
   - Codex CLI：$analyze-task {task-id}
 ```
 
+
+
 ## 完成检查清单
 
 - [ ] 创建了任务文件 `.agents/workspace/active/{task-id}/task.md`
@@ -175,7 +189,7 @@ Issue #{number} 已导入。
 ## 注意事项
 
 1. **Issue 验证**：在继续之前检查 Issue 是否存在
-2. **重复任务**：如果此 Issue 已有关联任务，在创建新任务前询问用户
+2. **重复任务**：如果此 Issue 已有关联任务，**默认复用**而非创建新任务（不询问用户）
 3. **下一步**：导入完成后，先执行 `analyze-task`，再进入 `plan-task`
 
 ## 错误处理

package/templates/.agents/skills/plan-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
@@ -167,10 +171,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

@@ -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. 验证前置条件
 
 检查必要文件：
@@ -167,10 +170,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}
 ```
 
 ## 完成检查清单