@fitlab-ai/agent-infra 0.4.1 → 0.4.3

package/templates/.agents/skills/implement-task/SKILL.md

@@ -24,7 +24,20 @@ Check these files first:
 
 If either file is missing, stop and ask the user to complete the prerequisite step.
 
-### 2. Determine the Input Plan and Implementation Round
+### 2. Ensure the Task Branch
+
+Read the branch field in `## Context` from `task.md` and check whether the current Git branch matches it.
+
+- if a task branch is already recorded, switch to it when the current branch does not match
+- if no branch is recorded, check whether the current branch follows the naming convention and belongs to this task
+  - if yes: record the current branch and continue
+  - if no: create and switch to a new task branch that follows the naming rule
+
+After this step, write the final branch name back to `task.md`.
+
+> Branch naming rules, Git commands, and edge-case handling live in `reference/branch-management.md`. Read `reference/branch-management.md` before executing this step.
+
+### 3. Determine the Input Plan and Implementation Round
 
 Scan `.agents/workspace/active/{task-id}/` and record:
 - the highest-round plan file as `{plan-artifact}`
@@ -33,7 +46,7 @@ Scan `.agents/workspace/active/{task-id}/` and record:
 
 If any `plan-r{N}.md` exists, read the highest-round plan file. Otherwise read `plan.md`.
 
-### 3. Read the Technical Plan
+### 4. Read the Technical Plan
 
 Read `{plan-artifact}` carefully and extract:
 - implementation steps
@@ -41,25 +54,25 @@ Read `{plan-artifact}` carefully and extract:
 - test strategy
 - constraints, risks, and any approved tradeoffs
 
-### 4. Implement the Code
+### 5. Implement the Code
 
 Follow `.agents/workflows/feature-development.yaml` and the plan in order.
 
 > Detailed implementation rules, testing discipline, and deviation handling live in `reference/implementation-rules.md`. Read `reference/implementation-rules.md` before executing this step.
 
-### 5. Run Test Verification
+### 6. Run Test Verification
 
 Use the project test command from the `test` skill and keep iterating until all required tests pass.
 
 If tests fail, Attempt to fix the issue and re-run tests first. Only stop when you confirm an external blocker, missing environment, or unclear requirement that is out of scope for the task.
 
-### 6. Write the Implementation Report
+### 7. Write the Implementation Report
 
 Create `.agents/workspace/active/{task-id}/{implementation-artifact}`.
 
 > Report structure, required sections, and the full template live in `reference/report-template.md`. Read `reference/report-template.md` before writing the report.
 
-### 7. Update Task Status
+### 8. Update Task Status
 
 Get the current time:
 
@@ -71,13 +84,36 @@ Update `.agents/workspace/active/{task-id}/task.md`:
 - `current_step`: implementation
 - `assigned_to`: {current agent}
 - `updated_at`: {current time}
+- review the `## Requirements` section and only change items from `- [ ]` to `- [x]` when they are clearly satisfied by this round's implemented code and passing tests
 - record `{implementation-artifact}` for Round `{implementation-round}`
 - append:
   `- {yyyy-MM-dd HH:mm:ss} — **Implementation (Round {N})** by {agent} — Code implemented, {n} files modified, {n} tests passed → {implementation-artifact}`
 
-### 8. Inform the User
+If task.md contains a valid `issue_number`, perform these sync actions (skip and continue on any failure; read `.agents/rules/issue-sync.md` first):
+- Set `status: in-progress` and refine `in:` labels from the branch diff by following `.agents/rules/issue-sync.md` (add/remove when a mapping exists, add-only when it does not)
+- Sync checked `## Requirements` items to the Issue body and publish the `{implementation-artifact}` comment
+- Create or update the `<!-- sync-issue:{task-id}:task -->` comment (follow the task.md comment sync rule in issue-sync.md)
+
+### 9. Verification Gate
+
+Run the verification gate to confirm the task artifact and sync state are valid:
+
+```bash
+node .agents/scripts/validate-artifact.js gate implement-task .agents/workspace/active/{task-id} {implementation-artifact} --format text
+```
+
+Handle the result as follows:
+- exit code 0 (all checks passed) -> continue to the "Inform User" step
+- exit code 1 (validation failed) -> fix the reported issues and run the gate again
+- exit code 2 (network blocked) -> stop and tell the user that human intervention is required
+
+Keep the gate output in your reply as fresh evidence. Do not claim completion without output from this run.
+
+### 10. Inform User
+
+> Execute this step only after the verification gate passes.
 
-Output the implementation summary and include all TUI command variants for the next review step.
+> **IMPORTANT**: All TUI command formats listed below must be output in full. Do not show only the format for the current AI agent. Use the output template in `reference/output-template.md`.
 
 ## Completion Checklist
 

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

@@ -24,7 +24,20 @@ description: "根据技术方案实施任务并输出报告"
 
 如果缺少任一文件，立即停止并提示用户先完成前置步骤。
 
-### 2. 确定输入方案与实现轮次
+### 2. 确保任务分支
+
+先读取 `task.md` 中 `## 上下文` 的分支字段，并检查当前 Git 分支是否匹配。
+
+- 已记录任务分支：当前分支不匹配时切换到该分支
+- 未记录任务分支：判断当前分支是否符合命名规范且属于当前任务
+  - 符合：记录当前分支并继续
+  - 不符合：按规范创建并切换到新的任务分支
+
+完成后，把最终使用的分支名回写到 `task.md`。
+
+> 分支命名规则、Git 命令和边界处理见 `reference/branch-management.md`。执行此步骤前，先读取 `reference/branch-management.md`。
+
+### 3. 确定输入方案与实现轮次
 
 扫描 `.agents/workspace/active/{task-id}/` 并记录：
 - 最高轮次的方案文件为 `{plan-artifact}`
@@ -33,7 +46,7 @@ description: "根据技术方案实施任务并输出报告"
 
 如果存在 `plan-r{N}.md`，读取最高轮次的方案文件；否则读取 `plan.md`。
 
-### 3. 阅读技术方案
+### 4. 阅读技术方案
 
 仔细阅读 `{plan-artifact}`，提取：
 - 实施步骤
@@ -41,25 +54,25 @@ description: "根据技术方案实施任务并输出报告"
 - 测试策略
 - 约束、风险与已批准的取舍
 
-### 4. 执行代码实现
+### 5. 执行代码实现
 
 按照 `.agents/workflows/feature-development.yaml` 和方案顺序实施。
 
 > 详细实现规则、测试纪律和偏离处理见 `reference/implementation-rules.md`。执行此步骤前，先读取 `reference/implementation-rules.md`。
 
-### 5. 运行测试验证
+### 6. 运行测试验证
 
 使用 `test` 技能中的项目测试命令，直到所有必需测试通过。
 
 如果测试失败，先尝试修复并重新运行测试。只有在确认存在外部阻塞、环境缺失或需求不明确且超出任务范围时，才可以停止。
 
-### 6. 编写实现报告
+### 7. 编写实现报告
 
 创建 `.agents/workspace/active/{task-id}/{implementation-artifact}`。
 
 > 报告结构、必填章节和完整模板见 `reference/report-template.md`。写报告前先读取 `reference/report-template.md`。
 
-### 7. 更新任务状态
+### 8. 更新任务状态
 
 获取当前时间：
 
@@ -71,13 +84,36 @@ date "+%Y-%m-%d %H:%M:%S"
 - `current_step`：implementation
 - `assigned_to`：{当前代理}
 - `updated_at`：{当前时间}
+- 审查 `## 需求` 段落，仅把本轮已由代码实现且有测试通过支撑的条目从 `- [ ]` 勾为 `- [x]`
 - 记录 Round `{implementation-round}` 的 `{implementation-artifact}`
 - 追加：
   `- {yyyy-MM-dd HH:mm:ss} — **Implementation (Round {N})** by {agent} — Code implemented, {n} files modified, {n} tests passed → {implementation-artifact}`
 
-### 8. 告知用户
+如果 task.md 中存在有效的 `issue_number`，执行以下同步操作（任一失败则跳过并继续；执行前先读取 `.agents/rules/issue-sync.md`）：
+- 设置 `status: in-progress`，并按 `.agents/rules/issue-sync.md` 的 `in:` label 同步规则，基于分支改动精修 `in:` label（有映射时可增可删，无映射时仅补充）
+- 同步 `## 需求` 中已勾选项到 Issue body，并发布 `{implementation-artifact}` 评论
+- 创建或更新 `<!-- sync-issue:{task-id}:task -->` 评论（按 issue-sync.md 的 task.md 评论同步规则）
+
+### 9. 完成校验
+
+运行完成校验，确认任务产物和同步状态符合规范：
+
+```bash
+node .agents/scripts/validate-artifact.js gate implement-task .agents/workspace/active/{task-id} {implementation-artifact} --format text
+```
+
+处理结果：
+- 退出码 0（全部通过）-> 继续到「告知用户」步骤
+- 退出码 1（校验失败）-> 根据输出修复问题后重新运行校验
+- 退出码 2（网络中断）-> 停止执行并告知用户需要人工介入
+
+将校验输出保留在回复中作为当次验证输出。没有当次校验输出，不得声明完成。
+
+### 10. 告知用户
+
+> 仅在校验通过后执行本步骤。
 
-输出实现摘要，并完整展示下一步代码审查的所有 TUI 命令格式。
+> **重要**：以下「下一步」中列出的所有 TUI 命令格式必须完整输出，不要只展示当前 AI 代理对应的格式。输出格式见 `reference/output-template.md`。
 
 ## 完成检查清单
 

package/templates/.agents/skills/implement-task/config/verify.json

@@ -0,0 +1,41 @@
+{
+  "skill": "implement-task",
+  "checks": {
+    "task-meta": {
+      "required_fields": [
+        "id",
+        "type",
+        "workflow",
+        "status",
+        "created_at",
+        "updated_at",
+        "current_step",
+        "assigned_to"
+      ],
+      "expected_step": "implementation"
+    },
+    "artifact": {
+      "file_pattern": "implementation.md|implementation-r{N}.md",
+      "required_sections": [
+        "变更文件",
+        "关键代码说明",
+        "测试结果",
+        "与方案的差异",
+        "供审查关注的内容"
+      ],
+      "freshness_minutes": 30
+    },
+    "activity-log": {
+      "expected_action_pattern": "Implementation \\(Round \\d+\\)",
+      "freshness_minutes": 30
+    },
+    "github-sync": {
+      "when": "issue_number_exists",
+      "expected_status_label": "status: in-progress",
+      "expected_comment_marker": "<!-- sync-issue:{task-id}:{artifact-stem} -->",
+      "verify_comment_content": true,
+      "verify_task_comment_content": true,
+      "sync_checked_requirements": true
+    }
+  }
+}

package/templates/.agents/skills/implement-task/reference/branch-management.md

@@ -0,0 +1,48 @@
+# Branch Management
+
+Read this file before ensuring the task branch.
+
+## Branch Naming Rule
+
+- Format: `{{project}}-{type}-{slug}`
+- project prefix: read the `project` field from `.agents/.airc.json`
+- `{type}`: read the `type` field from the task frontmatter
+- `{slug}`: derive a 3-6 word English kebab-case phrase from the task title
+
+## Branch Detection Flow
+
+Read these inputs first:
+- the `- **Branch**:` field under `## Context` in `task.md`
+- the current branch from `git branch --show-current`
+
+A recorded branch is valid when it has a non-empty value other than `TBD`, `to be created`, or `N/A`.
+
+Scenario A: `task.md` already records the task branch
+- if the current branch matches, continue
+- if it does not match, follow the "Create and Switch Commands" section below to switch to the recorded branch
+
+Scenario B: `task.md` has no task branch recorded
+- check whether the current branch follows the project naming convention (`{{project}}-{type}-{slug}`) and semantically belongs to this task
+- if yes: write the current branch name back to `task.md` and continue
+- if no: generate a new task branch name, create and switch using the "Create and Switch Commands" section below, then write it back to `task.md`
+
+## Create and Switch Commands
+
+Check branches in this order:
+
+```bash
+git branch --list {branch-name}
+git ls-remote --heads origin {branch-name}
+```
+
+- local branch exists: `git switch {branch-name}`
+- only remote branch exists: `git switch --track origin/{branch-name}`
+- neither exists: `git switch -c {branch-name}`
+
+If switching fails, stop and ask the user to resolve the branch or working tree conflict first.
+
+## task.md Write-back
+
+- update `- **Branch**: {branch-name}` under `## Context`
+- do not modify the other context fields
+- preserve the recorded branch value when updating task status later

package/templates/.agents/skills/implement-task/reference/branch-management.zh-CN.md

@@ -0,0 +1,49 @@
+# 分支管理
+
+在确保任务分支之前先读取本文件。
+
+## 分支名规则
+
+- 格式：`{{project}}-{type}-{slug}`
+- 项目前缀：读取 `.agents/.airc.json` 中的 `project`
+- `{type}`：读取 `task.md` frontmatter 中的 `type`
+- `{slug}`：根据任务标题提取 3-6 个英文关键词，转为 kebab-case
+
+## 分支检测流程
+
+先读取：
+- `task.md` 中 `## 上下文` 下的 `- **分支**：`
+- 当前分支：`git branch --show-current`
+
+有效已记录分支：
+- 有值，且不是 `待定`、`待创建`、`N/A` 或空字符串
+
+场景 A：`task.md` 已记录任务分支
+- 当前分支与记录值一致：直接继续
+- 当前分支不一致：按下方”创建与切换命令”章节切换到已记录分支
+
+场景 B：`task.md` 未记录任务分支
+- 判断当前分支是否符合项目分支命名规范（`{{project}}-{type}-{slug}`）且语义上属于当前任务
+- 符合：将当前分支名回写到 `task.md`，继续
+- 不符合：生成新的任务分支名，按下方”创建与切换命令”章节创建并切换，回写到 `task.md`
+
+## 创建与切换命令
+
+按以下顺序处理：
+
+```bash
+git branch --list {branch-name}
+git ls-remote --heads origin {branch-name}
+```
+
+- 本地分支已存在：`git switch {branch-name}`
+- 仅远程分支存在：`git switch --track origin/{branch-name}`
+- 本地和远程都不存在：`git switch -c {branch-name}`
+
+如果切换失败，立即停止并提示用户先处理工作区冲突或未解决的分支问题。
+
+## task.md 回写要求
+
+- 更新 `## 上下文` 中的 `- **分支**：{branch-name}`
+- 不修改其他上下文字段
+- 若本步骤已回写 `task.md`，后续更新任务状态时保留该分支值

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

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

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

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

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

@@ -58,7 +58,24 @@ Update task.md: `current_step` -> `requirement-analysis`.
   - {yyyy-MM-dd HH:mm:ss} — **Import Code Scanning Alert** by {agent} — Code Scanning alert #{alert-number} imported
   ```
 
-### 4. Inform User
+### 4. Verification Gate
+
+Run the verification gate to confirm the task artifact and sync state are valid:
+
+```bash
+node .agents/scripts/validate-artifact.js gate import-codescan .agents/workspace/active/{task-id} --format text
+```
+
+Handle the result as follows:
+- exit code 0 (all checks passed) -> continue to the "Inform User" step
+- exit code 1 (validation failed) -> fix the reported issues and run the gate again
+- exit code 2 (network blocked) -> stop and tell the user that human intervention is required
+
+Keep the gate output in your reply as fresh evidence. Do not claim completion without output from this run.
+
+### 5. Inform User
+
+> Execute this step only after the verification gate passes.
 
 > **IMPORTANT**: All TUI command formats listed below must be output in full. Do not show only the format for the current AI agent.
 
@@ -79,12 +96,6 @@ Next step:
   - Codex CLI: $analyze-task {task-id}
 ```
 
-## Notes
-
-1. **Severity priority**: Critical/High -> handle immediately. Medium -> schedule handling. Low -> can be deferred.
-2. **Scope**: this skill only imports the alert and creates the task; risk assessment is handled by `analyze-task`.
-3. **Follow-up**: after import, run `analyze-task` first, then decide whether to fix or dismiss.
-
 ## Completion Checklist
 
 - [ ] Retrieved and recorded the key alert information

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

@@ -58,7 +58,24 @@ date "+%Y-%m-%d %H:%M:%S"
   - {yyyy-MM-dd HH:mm:ss} — **Import Code Scanning Alert** by {agent} — Code Scanning alert #{alert-number} imported
   ```
 
-### 4. 告知用户
+### 4. 完成校验
+
+运行完成校验，确认任务产物和同步状态符合规范：
+
+```bash
+node .agents/scripts/validate-artifact.js gate import-codescan .agents/workspace/active/{task-id} --format text
+```
+
+处理结果：
+- 退出码 0（全部通过）-> 继续到「告知用户」步骤
+- 退出码 1（校验失败）-> 根据输出修复问题后重新运行校验
+- 退出码 2（网络中断）-> 停止执行并告知用户需要人工介入
+
+将校验输出保留在回复中作为当次验证输出。没有当次校验输出，不得声明完成。
+
+### 5. 告知用户
+
+> 仅在校验通过后执行本步骤。
 
 > **重要**：以下「下一步」中列出的所有 TUI 命令格式必须完整输出，不要只展示当前 AI 代理对应的格式。
 
@@ -79,12 +96,6 @@ Code Scanning 告警 #{alert-number} 已导入。
   - Codex CLI：$analyze-task {task-id}
 ```
 
-## 注意事项
-
-1. **严重程度优先级**：Critical/High -> 立即处理。Medium -> 计划处理。Low -> 可延后。
-2. **范围**：本技能仅负责导入告警并创建任务；风险评估由 `analyze-task` 负责。
-3. **后续动作**：导入后先执行 `analyze-task`，分析完成后再决定修复或关闭。
-
 ## 完成检查清单
 
 - [ ] 获取并记录了告警关键信息

package/templates/.agents/skills/import-codescan/config/verify.json

@@ -0,0 +1,24 @@
+{
+  "skill": "import-codescan",
+  "checks": {
+    "task-meta": {
+      "required_fields": [
+        "id",
+        "type",
+        "workflow",
+        "status",
+        "created_at",
+        "updated_at",
+        "current_step",
+        "assigned_to"
+      ],
+      "expected_step": "requirement-analysis",
+      "expected_status": "active"
+    },
+    "activity-log": {
+      "expected_action_pattern": "Import Code Scanning Alert",
+      "freshness_minutes": 30
+    },
+    "github-sync": null
+  }
+}

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

@@ -59,7 +59,24 @@ Update task.md: `current_step` -> `requirement-analysis`.
   - {yyyy-MM-dd HH:mm:ss} — **Import Dependabot Alert** by {agent} — Dependabot alert #{alert-number} imported
   ```
 
-### 4. Inform User
+### 4. Verification Gate
+
+Run the verification gate to confirm the task artifact and sync state are valid:
+
+```bash
+node .agents/scripts/validate-artifact.js gate import-dependabot .agents/workspace/active/{task-id} --format text
+```
+
+Handle the result as follows:
+- exit code 0 (all checks passed) -> continue to the "Inform User" step
+- exit code 1 (validation failed) -> fix the reported issues and run the gate again
+- exit code 2 (network blocked) -> stop and tell the user that human intervention is required
+
+Keep the gate output in your reply as fresh evidence. Do not claim completion without output from this run.
+
+### 5. Inform User
+
+> Execute this step only after the verification gate passes.
 
 > **IMPORTANT**: All TUI command formats listed below must be output in full. Do not show only the format for the current AI agent.
 
@@ -83,12 +100,6 @@ Next step:
   - Codex CLI: $analyze-task {task-id}
 ```
 
-## Notes
-
-1. **Severity priority**: Critical/High -> handle immediately. Medium -> schedule handling. Low -> can be deferred.
-2. **Scope**: this skill only imports the alert and creates the task; risk assessment is handled by `analyze-task`.
-3. **Follow-up**: after import, run `analyze-task` first, then decide whether to fix or dismiss.
-
 ## Completion Checklist
 
 - [ ] Retrieved and recorded the key alert information

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

@@ -59,7 +59,24 @@ date "+%Y-%m-%d %H:%M:%S"
   - {yyyy-MM-dd HH:mm:ss} — **Import Dependabot Alert** by {agent} — Dependabot alert #{alert-number} imported
   ```
 
-### 4. 告知用户
+### 4. 完成校验
+
+运行完成校验，确认任务产物和同步状态符合规范：
+
+```bash
+node .agents/scripts/validate-artifact.js gate import-dependabot .agents/workspace/active/{task-id} --format text
+```
+
+处理结果：
+- 退出码 0（全部通过）-> 继续到「告知用户」步骤
+- 退出码 1（校验失败）-> 根据输出修复问题后重新运行校验
+- 退出码 2（网络中断）-> 停止执行并告知用户需要人工介入
+
+将校验输出保留在回复中作为当次验证输出。没有当次校验输出，不得声明完成。
+
+### 5. 告知用户
+
+> 仅在校验通过后执行本步骤。
 
 > **重要**：以下「下一步」中列出的所有 TUI 命令格式必须完整输出，不要只展示当前 AI 代理对应的格式。
 
@@ -83,12 +100,6 @@ date "+%Y-%m-%d %H:%M:%S"
   - Codex CLI：$analyze-task {task-id}
 ```
 
-## 注意事项
-
-1. **严重程度优先级**：Critical/High -> 立即处理。Medium -> 计划处理。Low -> 可延后。
-2. **范围**：本技能仅负责导入告警并创建任务；风险评估由 `analyze-task` 负责。
-3. **后续动作**：导入后先执行 `analyze-task`，分析完成后再决定修复或关闭。
-
 ## 完成检查清单
 
 - [ ] 获取并记录了告警关键信息

package/templates/.agents/skills/import-dependabot/config/verify.json

@@ -0,0 +1,24 @@
+{
+  "skill": "import-dependabot",
+  "checks": {
+    "task-meta": {
+      "required_fields": [
+        "id",
+        "type",
+        "workflow",
+        "status",
+        "created_at",
+        "updated_at",
+        "current_step",
+        "assigned_to"
+      ],
+      "expected_step": "requirement-analysis",
+      "expected_status": "active"
+    },
+    "activity-log": {
+      "expected_action_pattern": "Import Dependabot Alert",
+      "freshness_minutes": 30
+    },
+    "github-sync": null
+  }
+}

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

@@ -22,6 +22,7 @@ gh issue view <issue-number> --json number,title,body,labels
 ```
 
 Extract: issue number, title, description, and labels.
+Use the Issue title as-is for the task title (preserve the Issue's original language).
 
 ### 2. Check for an Existing Task
 
@@ -69,7 +70,24 @@ Update `.agents/workspace/active/{task-id}/task.md`:
   - {yyyy-MM-dd HH:mm:ss} — **Import Issue** by {agent} — Issue #{number} imported
   ```
 
-### 5. Inform User
+### 5. Verification Gate
+
+Run the verification gate to confirm the task artifact and sync state are valid:
+
+```bash
+node .agents/scripts/validate-artifact.js gate import-issue .agents/workspace/active/{task-id} --format text
+```
+
+Handle the result as follows:
+- exit code 0 (all checks passed) -> continue to the "Inform User" step
+- exit code 1 (validation failed) -> fix the reported issues and run the gate again
+- exit code 2 (network blocked) -> stop and tell the user that human intervention is required
+
+Keep the gate output in your reply as fresh evidence. Do not claim completion without output from this run.
+
+### 6. Inform User
+
+> Execute this step only after the verification gate passes.
 
 > **IMPORTANT**: All TUI command formats listed below must be output in full. Do not show only the format for the current AI agent.
 

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

@@ -22,6 +22,7 @@ gh issue view <issue-number> --json number,title,body,labels
 ```
 
 提取：issue 编号、标题、描述、标签。
+任务标题直接使用 Issue 的原始标题（保持 Issue 标题的原始语言）。
 
 ### 2. 检查已有任务
 
@@ -69,7 +70,24 @@ date "+%Y-%m-%d %H:%M:%S"
   - {yyyy-MM-dd HH:mm:ss} — **Import Issue** by {agent} — Issue #{number} imported
   ```
 
-### 5. 告知用户
+### 5. 完成校验
+
+运行完成校验，确认任务产物和同步状态符合规范：
+
+```bash
+node .agents/scripts/validate-artifact.js gate import-issue .agents/workspace/active/{task-id} --format text
+```
+
+处理结果：
+- 退出码 0（全部通过）-> 继续到「告知用户」步骤
+- 退出码 1（校验失败）-> 根据输出修复问题后重新运行校验
+- 退出码 2（网络中断）-> 停止执行并告知用户需要人工介入
+
+将校验输出保留在回复中作为当次验证输出。没有当次校验输出，不得声明完成。
+
+### 6. 告知用户
+
+> 仅在校验通过后执行本步骤。
 
 > **重要**：以下「下一步」中列出的所有 TUI 命令格式必须完整输出，不要只展示当前 AI 代理对应的格式。