@fitlab-ai/agent-infra 0.4.1 → 0.4.3

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

@@ -68,20 +68,32 @@ ls .agents/workspace/blocked/{task-id}/task.md
 
 ### 6. 同步到 Issue（可选）
 
-检查 `task.md` 中是否存在 `issue_number` 字段，且其值不为空也不为 `N/A`。如果没有，**跳过此步骤，不输出任何内容**。
+检查 `task.md` 中是否存在有效的 `issue_number`。如果没有，跳过。
 
-如果存在有效的 `issue_number`，建议同步：
+> Issue 同步的 status label 规则见 `.agents/rules/issue-sync.md`。执行同步前先读取该文件。
 
-> **重要**：以下列出的所有 TUI 命令格式必须完整输出，不要只展示当前 AI 代理对应的格式。
+如果存在有效的 `issue_number`，直接设置 `status: blocked`。
 
+### 7. 完成校验
+
+运行完成校验，确认任务产物和同步状态符合规范：
+
+```bash
+node .agents/scripts/validate-artifact.js gate block-task .agents/workspace/blocked/{task-id} --format text
 ```
-（可选）同步阻塞状态到 Issue：
-  - Claude Code / OpenCode：/sync-issue {issue_number}
-  - Gemini CLI：/{{project}}:sync-issue {issue_number}
-  - Codex CLI：$sync-issue {issue_number}
-```
 
-### 7. 告知用户
+处理结果：
+- 退出码 0（全部通过）-> 继续到「告知用户」步骤
+- 退出码 1（校验失败）-> 根据输出修复问题后重新运行校验
+- 退出码 2（网络中断）-> 停止执行并告知用户需要人工介入
+
+将校验输出保留在回复中作为当次验证输出。没有当次校验输出，不得声明完成。
+
+### 8. 告知用户
+
+> 仅在校验通过后执行本步骤。
+
+> **重要**：以下「下一步」中列出的所有 TUI 命令格式必须完整输出，不要只展示当前 AI 代理对应的格式。
 
 输出格式：
 ```
@@ -94,35 +106,11 @@ ls .agents/workspace/blocked/{task-id}/task.md
 解除阻塞时执行：
   mv .agents/workspace/blocked/{task-id} .agents/workspace/active/{task-id}
   # 然后更新 task.md：status -> active，移除 blocked_at
-```
-
-## 输出模板
-
-添加到 task.md 的阻塞信息部分：
-
-```markdown
-## 阻塞信息
-
-### 摘要
-{阻塞原因的一行描述}
-
-### 问题描述
-{阻塞问题的详细描述}
-
-### 根本原因
-{分析为什么会被阻塞}
-
-### 已尝试的解决方案
-- {尝试了什么以及为什么没有成功}
-
-### 解除阻塞所需
-- {需要什么：信息、决策、资源等}
-
-### 解除阻塞条件
-{允许恢复工作的具体条件}
 
-### 备选方案
-{考虑过的任何变通方法或替代方案}
+下一步 - 检查任务状态（解除阻塞后）：
+  - Claude Code / OpenCode：/check-task {task-id}
+  - Gemini CLI：/agent-infra:check-task {task-id}
+  - Codex CLI：$check-task {task-id}
 ```
 
 ## 完成检查清单

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

@@ -0,0 +1,28 @@
+{
+  "skill": "block-task",
+  "checks": {
+    "task-meta": {
+      "required_fields": [
+        "id",
+        "type",
+        "workflow",
+        "status",
+        "created_at",
+        "updated_at",
+        "current_step",
+        "assigned_to",
+        "blocked_at"
+      ],
+      "expected_status": "blocked",
+      "require_blocked_at": true
+    },
+    "activity-log": {
+      "expected_action_pattern": "Blocked",
+      "freshness_minutes": 30
+    },
+    "github-sync": {
+      "when": "issue_number_exists",
+      "expected_status_label": "status: blocked"
+    }
+  }
+}

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

@@ -92,6 +92,8 @@ date "+%Y-%m-%d %H:%M:%S"
 
 ### 8. Inform User
 
+> **IMPORTANT**: All TUI command formats listed below must be output in full. Do not show only the format for the current AI agent.
+
 ```
 Code Scanning alert #{alert-number} dismissed.
 
@@ -103,6 +105,11 @@ Explanation: {explanation}
 View: {html_url}
 
 Note: it can be reopened on GitHub if necessary.
+
+Next step - complete and archive the task if a related task exists:
+  - Claude Code / OpenCode: /complete-task {task-id}
+  - Gemini CLI: /{{project}}:complete-task {task-id}
+  - Codex CLI: $complete-task {task-id}
 ```
 
 ## Notes

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

@@ -92,6 +92,8 @@ date "+%Y-%m-%d %H:%M:%S"
 
 ### 8. 告知用户
 
+> **重要**：以下「下一步」中列出的所有 TUI 命令格式必须完整输出，不要只展示当前 AI 代理对应的格式。
+
 ```
 Code Scanning 告警 #{alert-number} 已关闭。
 
@@ -103,6 +105,11 @@ Code Scanning 告警 #{alert-number} 已关闭。
 查看：{html_url}
 
 注意：如有需要，可在 GitHub 上重新打开。
+
+下一步 - 完成并归档任务（如有关联任务）：
+  - Claude Code / OpenCode：/complete-task {task-id}
+  - Gemini CLI：/agent-infra:complete-task {task-id}
+  - Codex CLI：$complete-task {task-id}
 ```
 
 ## 注意事项

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

@@ -100,6 +100,8 @@ date "+%Y-%m-%d %H:%M:%S"
 
 ### 8. Inform User
 
+> **IMPORTANT**: All TUI command formats listed below must be output in full. Do not show only the format for the current AI agent.
+
 ```
 Security alert #{alert-number} dismissed.
 
@@ -111,6 +113,11 @@ Explanation: {explanation}
 View: https://github.com/{owner}/{repo}/security/dependabot/{alert-number}
 
 Note: it can be reopened on GitHub if necessary.
+
+Next step - complete and archive the task if a related task exists:
+  - Claude Code / OpenCode: /complete-task {task-id}
+  - Gemini CLI: /{{project}}:complete-task {task-id}
+  - Codex CLI: $complete-task {task-id}
 ```
 
 ## Notes

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

@@ -100,6 +100,8 @@ date "+%Y-%m-%d %H:%M:%S"
 
 ### 8. 告知用户
 
+> **重要**：以下「下一步」中列出的所有 TUI 命令格式必须完整输出，不要只展示当前 AI 代理对应的格式。
+
 ```
 安全告警 #{alert-number} 已关闭。
 
@@ -111,6 +113,11 @@ date "+%Y-%m-%d %H:%M:%S"
 查看：https://github.com/{owner}/{repo}/security/dependabot/{alert-number}
 
 注意：如有需要，可在 GitHub 上重新打开。
+
+下一步 - 完成并归档任务（如有关联任务）：
+  - Claude Code / OpenCode：/complete-task {task-id}
+  - Gemini CLI：/agent-infra:complete-task {task-id}
+  - Codex CLI：$complete-task {task-id}
 ```
 
 ## 注意事项

package/templates/.agents/skills/commit/SKILL.md

@@ -44,12 +44,29 @@ date "+%Y-%m-%d %H:%M:%S"
 
 > The full four-case status matrix, prerequisite checks, and multi-TUI next-step commands live in `reference/task-status-update.md`. Read `reference/task-status-update.md` before updating task state.
 
+> **IMPORTANT**: When showing the next step, output every TUI command format in full and directly use the standard template from `reference/task-status-update.md`.
+
 Append the Commit Activity Log entry and choose exactly one next-step case:
 - final commit -> `complete-task {task-id}`
 - more work remains -> update task.md and stop
 - ready for review -> `review-task {task-id}`
 - ready for PR -> `create-pr`
 
+## 6. Verification Gate
+
+If this operation is associated with `{task-id}`, run the verification gate to confirm task metadata and sync state. If there is no task context, skip this step.
+
+```bash
+node .agents/scripts/validate-artifact.js gate commit .agents/workspace/active/{task-id}
+```
+
+Handle the result as follows:
+- exit code 0 (all checks passed) -> continue the remaining wrap-up steps
+- 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.
+
 ## Notes
 
 - Never commit secrets such as `.env`, credentials, or keys

package/templates/.agents/skills/commit/SKILL.zh-CN.md

@@ -44,12 +44,29 @@ date "+%Y-%m-%d %H:%M:%S"
 
 > 完整的 4 种状态分支、前置条件检查和多 TUI 下一步命令见 `reference/task-status-update.md`。更新任务状态前，先读取 `reference/task-status-update.md`。
 
+> **重要**：向用户展示下一步时，必须完整输出所有 TUI 命令格式，并直接使用 `reference/task-status-update.md` 中对应场景的标准模板。
+
 追加 Commit 的 Activity Log，并且只能选择一个下一步分支：
 - 最终提交 -> `complete-task {task-id}`
 - 还有后续工作 -> 更新 task.md 后停止
 - 准备审查 -> `review-task {task-id}`
 - 准备创建 PR -> `create-pr`
 
+## 6. 完成校验
+
+如果本次操作关联了 `{task-id}`，运行完成校验，确认任务元数据和同步状态符合规范；如果没有任务上下文，跳过本步骤。
+
+```bash
+node .agents/scripts/validate-artifact.js gate commit .agents/workspace/active/{task-id}
+```
+
+处理结果：
+- 退出码 0（全部通过）-> 继续后续收尾步骤
+- 退出码 1（校验失败）-> 根据输出修复问题后重新运行校验
+- 退出码 2（网络中断）-> 停止执行并告知用户需要人工介入
+
+将校验输出保留在回复中作为当次验证输出。没有当次校验输出，不得声明完成。
+
 ## 注意事项
 
 - 不要提交 `.env`、凭据、密钥等敏感文件

package/templates/.agents/skills/commit/config/verify.json

@@ -0,0 +1,22 @@
+{
+  "skill": "commit",
+  "checks": {
+    "task-meta": {
+      "required_fields": [
+        "id",
+        "type",
+        "workflow",
+        "status",
+        "created_at",
+        "updated_at",
+        "current_step",
+        "assigned_to"
+      ]
+    },
+    "activity-log": {
+      "expected_action_pattern": "Commit",
+      "freshness_minutes": 30
+    },
+    "github-sync": null
+  }
+}

package/templates/.agents/skills/commit/reference/task-status-update.md

@@ -82,7 +82,7 @@ Required next-step commands:
 
 ```text
 Next step - create Pull Request:
-  - Claude Code / OpenCode: /create-pr
-  - Gemini CLI: /agent-infra:create-pr
-  - Codex CLI: $create-pr
+  - Claude Code / OpenCode: /create-pr {task-id}
+  - Gemini CLI: /agent-infra:create-pr {task-id}
+  - Codex CLI: $create-pr {task-id}
 ```

package/templates/.agents/skills/commit/reference/task-status-update.zh-CN.md

@@ -82,7 +82,7 @@ date "+%Y-%m-%d %H:%M:%S"
 
 ```text
 下一步 - 创建 Pull Request：
-  - Claude Code / OpenCode: /create-pr
-  - Gemini CLI: /agent-infra:create-pr
-  - Codex CLI: $create-pr
+  - Claude Code / OpenCode: /create-pr {task-id}
+  - Gemini CLI: /agent-infra:create-pr {task-id}
+  - Codex CLI: $create-pr {task-id}
 ```

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

@@ -82,22 +82,36 @@ ls .agents/workspace/completed/{task-id}/task.md
 
 Confirm the task directory was successfully moved.
 
-### 6. Sync to Issue (Optional)
+### 6. Sync to Issue
 
-Check whether `task.md` includes an `issue_number` field whose value is neither empty nor `N/A`. If not, **skip this step and output nothing**.
+Check whether `task.md` includes a valid `issue_number`. If not, skip this step and output nothing.
 
-If a valid `issue_number` exists, optionally sync the completion status:
+> Issue sync rules live in `.agents/rules/issue-sync.md`. Read that file before syncing.
 
-> **IMPORTANT**: All TUI command formats listed below must be output in full. Do not show only the format for the current AI agent.
+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)
+- Backfill checked `## Requirements` items to the Issue body
+- 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 `<!-- sync-issue:{task-id}:summary -->`
 
+### 7. Verification Gate
+
+Run the verification gate to confirm the task artifact and sync state are valid:
+
+```bash
+node .agents/scripts/validate-artifact.js gate complete-task .agents/workspace/completed/{task-id} --format text
 ```
-(Optional) Sync completion status to the GitHub Issue:
-  - Claude Code / OpenCode: /sync-issue {issue_number}
-  - Gemini CLI: /{{project}}:sync-issue {issue_number}
-  - Codex CLI: $sync-issue {issue_number}
-```
 
-### 7. Inform User
+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.
+
+### 8. Inform User
+
+> Execute this step only after the verification gate passes.
 
 Output format:
 ```

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

@@ -82,22 +82,36 @@ ls .agents/workspace/completed/{task-id}/task.md
 
 确认任务目录已成功移动。
 
-### 6. 同步到 Issue（可选）
+### 6. 同步到 Issue
 
-检查 `task.md` 中是否存在 `issue_number` 字段，且其值不为空也不为 `N/A`。如果没有，**跳过此步骤，不输出任何内容**。
+检查 `task.md` 中是否存在有效的 `issue_number`。如果没有，跳过此步骤且不输出任何内容。
 
-如果存在有效的 `issue_number`，可选择同步完成状态：
+> Issue 同步规则见 `.agents/rules/issue-sync.md`。执行同步前先读取该文件。
 
-> **重要**：以下列出的所有 TUI 命令格式必须完整输出，不要只展示当前 AI 代理对应的格式。
+如果存在有效的 `issue_number`：
+- 先按 `.agents/rules/issue-sync.md` 的补发规则扫描并补发未发布的 `task.md`、`analysis*.md`、`plan*.md`、`implementation*.md`、`review*.md`、`refinement*.md` 评论（`task.md` 走幂等更新路径）
+- 兜底同步 `## 需求` 中已勾选的条目到 Issue body
+- 不要设置 `status:` label — Issue 关闭后 status label 会被自动清除
+- 最后创建或更新 `<!-- sync-issue:{task-id}:summary -->` 标记的 summary 评论
 
+### 7. 完成校验
+
+运行完成校验，确认任务产物和同步状态符合规范：
+
+```bash
+node .agents/scripts/validate-artifact.js gate complete-task .agents/workspace/completed/{task-id} --format text
 ```
-（可选）同步完成状态到 GitHub Issue：
-  - Claude Code / OpenCode：/sync-issue {issue_number}
-  - Gemini CLI：/{{project}}:sync-issue {issue_number}
-  - Codex CLI：$sync-issue {issue_number}
-```
 
-### 7. 告知用户
+处理结果：
+- 退出码 0（全部通过）-> 继续到「告知用户」步骤
+- 退出码 1（校验失败）-> 根据输出修复问题后重新运行校验
+- 退出码 2（网络中断）-> 停止执行并告知用户需要人工介入
+
+将校验输出保留在回复中作为当次验证输出。没有当次校验输出，不得声明完成。
+
+### 8. 告知用户
+
+> 仅在校验通过后执行本步骤。
 
 输出格式：
 ```

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

@@ -0,0 +1,30 @@
+{
+  "skill": "complete-task",
+  "checks": {
+    "task-meta": {
+      "required_fields": [
+        "id",
+        "type",
+        "workflow",
+        "status",
+        "created_at",
+        "updated_at",
+        "current_step",
+        "assigned_to",
+        "completed_at"
+      ],
+      "expected_status": "completed",
+      "require_completed_at": true
+    },
+    "activity-log": {
+      "expected_action_pattern": "Completed",
+      "freshness_minutes": 30
+    },
+    "github-sync": {
+      "when": "issue_number_exists",
+      "expected_comment_marker": "<!-- sync-issue:{task-id}:summary -->",
+      "verify_task_comment_content": true,
+      "sync_checked_requirements": true
+    }
+  }
+}

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

@@ -10,6 +10,7 @@ Create the base GitHub Issue from `task.md` and write `issue_number` back to the
 ## Boundary / Critical Rules
 
 - Build the Issue title and body from `task.md` only
+- Issue title format: `type(scope): description` - map `type` from task.md (`feature` -> `feat`, `bugfix` -> `fix`, `refactor` -> `refactor`, `docs` -> `docs`, `chore` -> `chore`), infer scope from the affected module (omit it if unclear), and use the task title from task.md verbatim for the description (do not translate or rewrite)
 - Do not read `analysis.md`, `plan.md`, `implementation.md`, or review artifacts
 - The only durable outputs are the GitHub Issue and the `issue_number` update in task.md
 - After executing this skill, you **must** immediately update task.md
@@ -26,7 +27,7 @@ If `issue_number` already exists and is not empty or `N/A`, confirm with the use
 
 ### 2. Extract Task Information
 
-Extract the title, `## Description`, `## Requirements`, `type`, and `milestone` from task.md.
+Extract the title, `## Description`, `## Requirements`, `type`, and `milestone` from task.md. Build the Issue title by mapping task.md `type` to a Conventional Commits type, inferring scope, and formatting it as `cc_type(scope): task_title` or `cc_type: task_title` when scope is unclear.
 
 ### 3. Build Issue Content
 
@@ -53,9 +54,44 @@ date "+%Y-%m-%d %H:%M:%S"
 
 Write back `issue_number`, update `updated_at`, and append the Create Issue Activity Log entry.
 
-### 6. Inform User
+### 5.1 Backfill Existing Artifacts
 
-Show the Issue number, URL, labels, Issue Type, milestone result, confirm that `issue_number` was written back, and include the next `sync-issue` command in every TUI format.
+If artifact files already exist in the task directory, backfill them in this order:
+
+1. `task.md` -> `<!-- sync-issue:{task-id}:task -->` comment (idempotent create or update)
+2. Backfill existing `analysis*.md`, `plan*.md`, `implementation*.md`, `review*.md`, and `refinement*.md` files in filename order
+
+Every backfill action must follow the raw publishing, task.md sync, and chunking rules in `.agents/rules/issue-sync.md`.
+
+### 6. Verification Gate
+
+Run the verification gate to confirm the task artifact and sync state are valid:
+
+```bash
+node .agents/scripts/validate-artifact.js gate create-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.
+
+### 7. 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.
+
+Show the Issue number, URL, labels, Issue Type, milestone result, confirm that `issue_number` was written back, and include the next-step commands in every TUI format:
+
+```
+Next step - run requirements analysis:
+  - Claude Code / OpenCode: /analyze-task {task-id}
+  - Gemini CLI: /{{project}}:analyze-task {task-id}
+  - Codex CLI: $analyze-task {task-id}
+```
 
 ## Completion Checklist
 
@@ -63,7 +99,7 @@ Show the Issue number, URL, labels, Issue Type, milestone result, confirm that `
 - [ ] Used `task.md` as the only content source
 - [ ] Recorded `issue_number` in task.md
 - [ ] Updated `updated_at` and appended the Activity Log entry
-- [ ] Included all TUI formats for the next `sync-issue` step
+- [ ] Included all TUI formats for the next-step commands
 
 ## STOP
 
@@ -71,7 +107,7 @@ Stop after the checklist. Do not start detailed progress sync here.
 
 ## Notes
 
-- `create-issue` creates the base Issue; `sync-issue` publishes detailed progress later
+- `create-issue` creates the base Issue; later status, comments, and checkboxes are maintained by workflow skills and GitHub Actions
 - If no valid labels survive filtering, create the Issue without labels instead of failing
 - If Issue Type or milestone setup fails, continue and record the fallback outcome
 

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

@@ -10,6 +10,7 @@ description: "从任务文件创建 GitHub Issue"
 ## 行为边界 / 关键规则
 
 - Issue 标题和正文只能来自 `task.md`
+- Issue 标题格式为 `type(scope): 描述`——type 从 task.md 的 `type` 字段映射（feature→feat, bugfix→fix, refactor→refactor, docs→docs, chore→chore），scope 从受影响模块推断（无法确定时省略），描述使用 task.md 中的任务标题原文（不要翻译或改写）
 - 不要读取 `analysis.md`、`plan.md`、`implementation.md` 或审查产物
 - 持久产物只有 GitHub Issue 本身，以及 task.md 中的 `issue_number` 更新
 - 执行本技能后，你**必须**立即更新 task.md
@@ -26,7 +27,7 @@ description: "从任务文件创建 GitHub Issue"
 
 ### 2. 提取任务信息
 
-从 task.md 提取标题、`## Description`、`## Requirements`、`type` 和 `milestone`。
+从 task.md 提取标题、`## Description`、`## Requirements`、`type` 和 `milestone`。构造 Issue 标题：将 task.md 的 `type` 映射为 Conventional Commits type，推断 scope，拼接为 `cc_type(scope): task_title` 或 `cc_type: task_title`（scope 不确定时省略）。
 
 ### 3. 构建 Issue 内容
 
@@ -53,9 +54,44 @@ date "+%Y-%m-%d %H:%M:%S"
 
 回写 `issue_number`，更新 `updated_at`，并追加 Create Issue 的 Activity Log。
 
-### 6. 告知用户
+### 5.1 补发已有产物
 
-展示 Issue 编号、URL、labels、Issue Type、milestone 结果，确认 `issue_number` 已回写，并完整输出所有 TUI 里的下一步 `sync-issue` 命令。
+如果任务目录中已存在产物文件，按以下顺序补发：
+
+1. `task.md` → `<!-- sync-issue:{task-id}:task -->` 评论（幂等创建或更新）
+2. 按文件名排序补发已存在的 `analysis*.md`、`plan*.md`、`implementation*.md`、`review*.md`、`refinement*.md`
+
+所有补发动作都必须遵循 `.agents/rules/issue-sync.md` 的原文发布、task.md 同步和分片规则。
+
+### 6. 完成校验
+
+运行完成校验，确认任务产物和同步状态符合规范：
+
+```bash
+node .agents/scripts/validate-artifact.js gate create-issue .agents/workspace/active/{task-id} --format text
+```
+
+处理结果：
+- 退出码 0（全部通过）-> 继续到「告知用户」步骤
+- 退出码 1（校验失败）-> 根据输出修复问题后重新运行校验
+- 退出码 2（网络中断）-> 停止执行并告知用户需要人工介入
+
+将校验输出保留在回复中作为当次验证输出。没有当次校验输出，不得声明完成。
+
+### 7. 告知用户
+
+> 仅在校验通过后执行本步骤。
+
+> **重要**：以下「下一步」中列出的所有 TUI 命令格式必须完整输出，不要只展示当前 AI 代理对应的格式。
+
+展示 Issue 编号、URL、labels、Issue Type、milestone 结果，确认 `issue_number` 已回写，并完整输出所有 TUI 里的下一步命令：
+
+```
+下一步 - 执行需求分析：
+  - Claude Code / OpenCode：/analyze-task {task-id}
+  - Gemini CLI：/agent-infra:analyze-task {task-id}
+  - Codex CLI：$analyze-task {task-id}
+```
 
 ## 完成检查清单
 
@@ -63,7 +99,7 @@ date "+%Y-%m-%d %H:%M:%S"
 - [ ] 已仅使用 `task.md` 作为内容来源
 - [ ] 已在 task.md 中记录 `issue_number`
 - [ ] 已更新 `updated_at` 并追加 Activity Log
-- [ ] 已输出所有 TUI 格式的 `sync-issue` 下一步命令
+- [ ] 已输出所有 TUI 格式的下一步命令
 
 ## 停止
 
@@ -71,7 +107,7 @@ date "+%Y-%m-%d %H:%M:%S"
 
 ## 注意事项
 
-- `create-issue` 只负责创建基础 Issue；详细进度由 `sync-issue` 发布
+- `create-issue` 只负责创建基础 Issue；后续状态、评论和复选框由工作流技能与 GitHub Actions 维护
 - 如果过滤后没有有效 label，允许不带 label 创建 Issue
 - 如果 Issue Type 或 milestone 设置失败，继续执行并记录结果
 

package/templates/.agents/skills/create-issue/config/verify.json

@@ -0,0 +1,27 @@
+{
+  "skill": "create-issue",
+  "checks": {
+    "task-meta": {
+      "required_fields": [
+        "id",
+        "type",
+        "workflow",
+        "status",
+        "created_at",
+        "updated_at",
+        "current_step",
+        "assigned_to"
+      ],
+      "require_issue_number": true
+    },
+    "activity-log": {
+      "expected_action_pattern": "Create Issue",
+      "freshness_minutes": 30
+    },
+    "github-sync": {
+      "when": "issue_number_exists",
+      "issue_must_exist": true,
+      "verify_task_comment_content": true
+    }
+  }
+}

package/templates/.agents/skills/create-issue/reference/label-and-type.md

@@ -28,7 +28,8 @@ Fallback label mapping:
 | `enhancement` | `type: enhancement` |
 | `docs`, `documentation` | `type: documentation` |
 | `dependency-upgrade` | `type: dependency-upgrade` |
-| `task`, `chore`, `refactor`, `refactoring` | `type: task` |
+| `task`, `chore` | `type: task` |
+| `refactor`, `refactoring` | `type: enhancement` |
 | other values | skip |
 
 Issue Type fallback mapping:
@@ -56,22 +57,20 @@ gh api "orgs/$owner/issue-types" --jq '.[].name'
 gh api "repos/$repo/issues/{issue-number}" -X PATCH -f type="{issue-type}" --silent
 ```
 
-`in:` labels:
+`in:` labels (coarse selection):
 
 ```bash
 gh label list --search "in:" --limit 50 --json name --jq '.[].name'
 gh issue edit {issue-number} --add-label "in: {module}"
 ```
 
-Only add relevant `in:` labels. Do not remove existing `in:` labels, and do not fail Issue creation when `in:` labels are unavailable or irrelevant.
+Use the returned labels to do semantic matching against the task.md title and description:
+- add a label when the task **explicitly mentions** a module (for example, "fix CLI argument parsing" -> `in: cli`)
+- add a label when the task **strongly implies** a module
+- skip the label when the mapping is ambiguous or uncertain
 
-Skip unavailable labels, Issue Types, or milestones without failing the Issue creation flow.
+Principle: prefer missing labels over wrong labels. Coarse selection does not need to be perfect because implement-task / create-pr will refine `in:` labels from actual changed files later.
 
-Final user output must include every TUI `sync-issue` command format:
+Only add relevant `in:` labels. Do not fail Issue creation when `in:` labels are unavailable or irrelevant.
 
-```text
-Next step - sync progress to the Issue:
-  - Claude Code / OpenCode: /sync-issue {task-id}
-  - Gemini CLI: /agent-infra:sync-issue {task-id}
-  - Codex CLI: $sync-issue {task-id}
-```
+Skip unavailable labels, Issue Types, or milestones without failing the Issue creation flow.