@fitlab-ai/agent-infra 0.4.3 → 0.4.5

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

@@ -154,6 +154,8 @@ function runCheck(type, context) {
       return checkArtifact(context);
     case "activity-log":
       return checkActivityLog(context);
+    case "completion-checklist":
+      return checkCompletionChecklist(context);
     case "github-sync":
       return checkGithubSync(context);
     default:
@@ -176,7 +178,7 @@ function checkTaskMeta({ taskDir, config }) {
     return failResult("task-meta", `Missing required fields: ${missingFields.join(", ")}`);
   }
 
-  const invalidDates = ["created_at", "updated_at", "completed_at", "blocked_at"]
+  const invalidDates = ["created_at", "updated_at", "completed_at", "blocked_at", "cancelled_at"]
     .filter((field) => !isBlank(metadata[field]) && !DATE_TIME_PATTERN.test(metadata[field]));
   if (invalidDates.length > 0) {
     return failResult("task-meta", `Invalid date format in: ${invalidDates.join(", ")}`);
@@ -216,6 +218,10 @@ function checkTaskMeta({ taskDir, config }) {
     return failResult("task-meta", "Expected blocked_at to be present");
   }
 
+  if (config.require_cancelled_at && isBlank(metadata.cancelled_at)) {
+    return failResult("task-meta", "Expected cancelled_at to be present");
+  }
+
   if (config.match_task_dir !== false) {
     const expectedTaskId = path.basename(taskDir);
     if (metadata.id !== expectedTaskId) {
@@ -338,6 +344,43 @@ function checkActivityLog({ taskDir, config }) {
   return passResult("activity-log", `Latest entry '${latestAction}' at ${latestTimestamp}`);
 }
 
+function checkCompletionChecklist({ taskDir, config }) {
+  const task = loadTask(taskDir);
+  if (!task.ok) {
+    return failResult("completion-checklist", task.message);
+  }
+
+  const checklist = getSectionContent(task.content, ["完成检查清单", "Completion Checklist"]);
+  if (!checklist) {
+    return failResult("completion-checklist", "Completion Checklist section not found");
+  }
+
+  const items = checklist
+    .split(/\r?\n/)
+    .map((line) => line.trim())
+    .filter((line) => /^- \[(?: |x|X)\] .+$/.test(line));
+
+  if (items.length === 0) {
+    return failResult("completion-checklist", "Completion Checklist has no checkbox items");
+  }
+
+  if (config.require_all_checked) {
+    const unchecked = items
+      .map((line) => line.match(/^- \[ \] (.+)$/))
+      .filter(Boolean)
+      .map((match) => match[1].trim());
+
+    if (unchecked.length > 0) {
+      return failResult(
+        "completion-checklist",
+        `Completion Checklist has unchecked items: ${unchecked.join(", ")}`
+      );
+    }
+  }
+
+  return passResult("completion-checklist", `Completion Checklist valid (${items.length} items checked)`);
+}
+
 function checkGithubSync({ taskDir, config, artifactFile }) {
   const context = buildSyncContext({ taskDir, config, artifactFile });
   if (context.earlyReturn) {
@@ -356,7 +399,9 @@ function checkGithubSync({ taskDir, config, artifactFile }) {
     checkCommentContent,
     checkTaskCommentContent,
     checkInLabelsMatchPr,
-    checkSyncedRequirements
+    checkSyncedRequirements,
+    checkIssueType,
+    checkMilestone
   ];
 
   for (const subCheck of subChecks) {
@@ -536,7 +581,7 @@ function fetchRemoteData(context) {
     "view",
     String(context.issueNumber),
     "--json",
-    "state,labels,body"
+    "state,labels,body,milestone"
   ], context.taskDir));
   if (!issueResult.ok) {
     return {
@@ -599,14 +644,37 @@ function fetchRemoteData(context) {
     prComments = flattenComments(prCommentsResult.value);
   }
 
+  let issueType;
+  if (context.config.verify_issue_type) {
+    const issueTypeResult = withRetry(() => ghText([
+      "api",
+      `repos/${context.ownerRepo}/issues/${context.issueNumber}`,
+      "--jq",
+      ".type.name // empty"
+    ], context.taskDir));
+
+    if (issueTypeResult.ok) {
+      issueType = issueTypeResult.value || null;
+    }
+  }
+
   let prLabels = null;
-  if (context.config.verify_in_labels_match_pr && context.prNumber) {
+  let prMilestone;
+  if ((context.config.verify_in_labels_match_pr || context.config.verify_milestone) && context.prNumber) {
+    const prFields = [];
+    if (context.config.verify_in_labels_match_pr) {
+      prFields.push("labels");
+    }
+    if (context.config.verify_milestone) {
+      prFields.push("milestone");
+    }
+
     const prResult = withRetry(() => ghJson([
       "pr",
       "view",
       String(context.prNumber),
       "--json",
-      "labels"
+      prFields.join(",")
     ], context.taskDir));
 
     if (!prResult.ok) {
@@ -617,14 +685,21 @@ function fetchRemoteData(context) {
       };
     }
 
-    prLabels = extractLabelNames(prResult.value?.labels);
+    prLabels = context.config.verify_in_labels_match_pr
+      ? extractLabelNames(prResult.value?.labels)
+      : null;
+    prMilestone = context.config.verify_milestone
+      ? prResult.value?.milestone ?? null
+      : undefined;
   }
 
   return {
     issue,
     comments,
     prComments,
-    prLabels
+    prLabels,
+    issueType,
+    prMilestone
   };
 }
 
@@ -810,6 +885,59 @@ function checkSyncedRequirements(context, remoteData) {
   );
 }
 
+function checkIssueType(context, remoteData) {
+  if (!context.config.verify_issue_type) {
+    return null;
+  }
+
+  if (remoteData.issueType === undefined) {
+    return null;
+  }
+
+  if (!remoteData.issueType) {
+    return failResult(
+      "github-sync",
+      `Issue #${context.issueNumber} has no Issue Type set`,
+      "check_failed"
+    );
+  }
+
+  const expectedType = mapTaskTypeToIssueType(context.task.metadata.type);
+  if (expectedType && remoteData.issueType !== expectedType) {
+    return failResult(
+      "github-sync",
+      `Issue #${context.issueNumber} has type '${remoteData.issueType}', expected '${expectedType}' (from task type '${context.task.metadata.type}')`,
+      "check_failed"
+    );
+  }
+
+  return null;
+}
+
+function checkMilestone(context, remoteData) {
+  if (!context.config.verify_milestone) {
+    return null;
+  }
+
+  if (!remoteData.issue?.milestone?.title) {
+    return failResult(
+      "github-sync",
+      `Issue #${context.issueNumber} has no milestone set`,
+      "check_failed"
+    );
+  }
+
+  if (context.prNumber && remoteData.prMilestone !== undefined && !remoteData.prMilestone?.title) {
+    return failResult(
+      "github-sync",
+      `PR #${context.prNumber} has no milestone set`,
+      "check_failed"
+    );
+  }
+
+  return null;
+}
+
 function findCommentByMarker(comments, marker) {
   return (comments || []).find((comment) => typeof comment.body === "string" && comment.body.includes(marker)) || null;
 }
@@ -945,6 +1073,24 @@ function extractLabelNames(labels) {
     .filter((label) => typeof label === "string" && label.length > 0);
 }
 
+function mapTaskTypeToIssueType(taskType) {
+  const mapping = {
+    bug: "Bug",
+    bugfix: "Bug",
+    enhancement: "Feature",
+    feature: "Feature",
+    task: "Task",
+    documentation: "Task",
+    "dependency-upgrade": "Task",
+    chore: "Task",
+    docs: "Task",
+    refactor: "Task",
+    refactoring: "Task"
+  };
+
+  return mapping[taskType] || "Task";
+}
+
 function arraysEqual(left, right) {
   if (left.length !== right.length) {
     return false;
@@ -992,6 +1138,28 @@ function resolveOwnerRepo(taskDir) {
 }
 
 function ghJson(args, cwd) {
+  const result = ghCommand(args, cwd);
+  if (!result.ok) {
+    return result;
+  }
+
+  try {
+    return { ok: true, value: JSON.parse(result.value || "null") };
+  } catch (error) {
+    return { ok: false, type: "network_error", message: `Invalid JSON from gh: ${error.message}` };
+  }
+}
+
+function ghText(args, cwd) {
+  const result = ghCommand(args, cwd);
+  if (!result.ok) {
+    return result;
+  }
+
+  return { ok: true, value: String(result.value || "").trim() };
+}
+
+function ghCommand(args, cwd) {
   const result = spawnSync("gh", args, {
     cwd,
     encoding: "utf8",
@@ -1004,11 +1172,7 @@ function ghJson(args, cwd) {
     return { ok: false, type: classified.type, message: classified.message };
   }
 
-  try {
-    return { ok: true, value: JSON.parse(result.stdout || "null") };
-  } catch (error) {
-    return { ok: false, type: "network_error", message: `Invalid JSON from gh: ${error.message}` };
-  }
+  return { ok: true, value: result.stdout };
 }
 
 function ghPaginatedJson(args, cwd) {

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

@@ -35,7 +35,9 @@
       "expected_status_label": "status: pending-design-work",
       "expected_comment_marker": "<!-- sync-issue:{task-id}:{artifact-stem} -->",
       "verify_comment_content": true,
-      "verify_task_comment_content": true
+      "verify_task_comment_content": true,
+      "verify_issue_type": true,
+      "verify_milestone": true
     }
   }
 }

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

@@ -0,0 +1,142 @@
+---
+name: cancel-task
+description: "Cancel an unneeded task and archive it"
+---
+
+# Cancel Task
+
+## Boundary / Critical Rules
+
+- This command terminates a task that no longer needs to continue and archives it into `completed/`
+- Cancel only when the task no longer needs implementation, review, or follow-up work
+- When a valid `issue_number` exists, GitHub Issue sync is required
+
+## Steps
+
+### 1. Verify Task Exists
+
+Check these directories in order:
+- `.agents/workspace/active/{task-id}/`
+- `.agents/workspace/blocked/{task-id}/`
+- `.agents/workspace/completed/{task-id}/`
+
+Handling rules:
+- If found in `active/` or `blocked/`: continue
+- If found only in `completed/`: inform the user the task is already archived and stop
+- If not found anywhere: prompt `Task {task-id} not found`
+
+### 2. Choose the Cancellation Label
+
+Infer the GitHub Issue closing label from the cancellation reason:
+- `status: superseded`: reason implies duplicate, replaced, merged into, or already covered by another Issue or PR
+- `status: invalid`: reason implies invalid report, no real problem, cannot reproduce, or no issue after investigation
+- `status: declined`: reason implies not planned, deprioritized, or explicitly rejected
+- If nothing matches: fall back to `status: declined`
+
+When syncing to the Issue, replace any existing `status:` labels with the inferred label.
+
+### 3. Update Task Metadata
+
+Get the current time:
+
+```bash
+date "+%Y-%m-%d %H:%M:%S"
+```
+
+Update `task.md` in the task directory:
+- `status`: completed
+- `cancelled_at`: {current timestamp}
+- `cancel_reason`: {cancellation reason}
+- `updated_at`: {current timestamp}
+- **Append** to `## Activity Log` (do NOT overwrite previous entries):
+  ```
+  - {yyyy-MM-dd HH:mm:ss} — **Cancelled** by {agent} — {one-line cancellation reason}
+  ```
+
+### 4. Archive the Task
+
+Move the task directory into `.agents/workspace/completed/{task-id}`.
+
+If the source directory is `blocked/`, move it from `blocked/`; if it is `active/`, move it from `active/`.
+
+### 5. Verify the Archive
+
+```bash
+ls .agents/workspace/completed/{task-id}/task.md
+```
+
+Confirm the task directory was moved successfully.
+
+### 6. Sync to Issue
+
+Check whether `task.md` contains a valid `issue_number`. If not, skip this step.
+
+> Issue sync rules live in `.agents/rules/issue-sync.md`. Read that file before syncing.
+
+If a valid `issue_number` exists:
+- Replace all `status:` labels with the label inferred in Step 2
+- Remove all `in:` labels
+- Remove the milestone
+- Remove all assignees
+- Publish a cancellation comment using the marker `<!-- sync-issue:{task-id}:cancel -->`
+- Create or update the `<!-- sync-issue:{task-id}:task -->` comment using the task-comment sync rules from `.agents/rules/issue-sync.md`
+- Close the Issue: `gh issue close {issue-number} --reason "not planned"`
+
+The cancellation comment must include at least:
+- the cancellation reason
+- the selected `status:` label
+
+### 7. Verification Gate
+
+Run the verification gate to confirm the archived task and sync state are valid:
+
+```bash
+node .agents/scripts/validate-artifact.js gate cancel-task .agents/workspace/completed/{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.
+
+### 8. 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.
+
+Output format:
+```
+Task {task-id} cancelled and archived.
+
+Cancellation reason: {reason}
+GitHub label: {status-label or skipped}
+Archived to: .agents/workspace/completed/{task-id}/
+
+Next step - inspect the archived task:
+  - Claude Code / OpenCode: /check-task {task-id}
+  - Gemini CLI: /{{project}}:check-task {task-id}
+  - Codex CLI: $check-task {task-id}
+```
+
+## Completion Checklist
+
+- [ ] Recorded the cancellation reason and updated task.md
+- [ ] Moved the task directory into `.agents/workspace/completed/`
+- [ ] Completed GitHub sync when an Issue exists
+- [ ] Ran and passed the verification gate
+- [ ] Showed the full next-step command set to the user
+
+## Notes
+
+1. Cancelled tasks reuse the `completed` status instead of introducing `cancelled`
+2. Use `cancelled_at` and `cancel_reason` to distinguish cancellation from normal completion
+3. If closing the Issue fails, do not claim the cancellation is complete
+
+## Error Handling
+
+- Task not found: `Task {task-id} not found`
+- Task already archived: inform the user it is already in `completed/`
+- Issue sync failed: keep the local archive result and tell the user manual GitHub follow-up is required

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

@@ -0,0 +1,142 @@
+---
+name: cancel-task
+description: "取消不再需要的任务并归档"
+---
+
+# 取消任务
+
+## 行为边界 / 关键规则
+
+- 本命令用于终止一个不再需要继续执行的任务，并归档到 `completed/`
+- 只有在确认该任务无需继续实现、审查或修复时才可取消
+- 有效 `issue_number` 存在时，GitHub Issue 同步属于必做项
+
+## 执行步骤
+
+### 1. 验证任务存在
+
+依次检查以下目录：
+- `.agents/workspace/active/{task-id}/`
+- `.agents/workspace/blocked/{task-id}/`
+- `.agents/workspace/completed/{task-id}/`
+
+处理规则：
+- 如果在 `active/` 或 `blocked/` 中找到：继续
+- 如果只在 `completed/` 中找到：告知用户任务已归档，停止
+- 如果都不存在：提示 `Task {task-id} not found`
+
+### 2. 判断取消标签
+
+根据取消原因推断 GitHub Issue 关闭标签：
+- `status: superseded`：原因包含“重复”、“替代”、“合并到”、“已由 #123 / PR 替代”等语义
+- `status: invalid`：原因包含“误报”、“不存在”、“无法复现”、“排查后无问题”等语义
+- `status: declined`：原因包含“不做”、“暂不实现”、“优先级调整”、“方案否决”等语义
+- 以上都不匹配：回退到 `status: declined`
+
+后续同步到 Issue 时，使用最终推断结果替换现有 `status:` labels。
+
+### 3. 更新任务元数据
+
+获取当前时间：
+
+```bash
+date "+%Y-%m-%d %H:%M:%S"
+```
+
+更新任务目录中的 `task.md`：
+- `status`：completed
+- `cancelled_at`：{当前时间戳}
+- `cancel_reason`：{取消原因}
+- `updated_at`：{当前时间戳}
+- **追加**到 `## Activity Log`（不要覆盖之前记录）：
+  ```
+  - {yyyy-MM-dd HH:mm:ss} — **Cancelled** by {agent} — {一行取消原因}
+  ```
+
+### 4. 归档任务
+
+将任务目录移动到 `.agents/workspace/completed/{task-id}`。
+
+如果源目录在 `blocked/`，从 `blocked/` 移动；如果源目录在 `active/`，从 `active/` 移动。
+
+### 5. 验证归档
+
+```bash
+ls .agents/workspace/completed/{task-id}/task.md
+```
+
+确认任务目录已成功移动。
+
+### 6. 同步到 Issue
+
+检查 `task.md` 中是否存在有效的 `issue_number`。如果没有，跳过此步骤。
+
+> Issue 同步规则见 `.agents/rules/issue-sync.md`。执行同步前先读取该文件。
+
+如果存在有效的 `issue_number`：
+- 替换所有 `status:` labels，并设置步骤 2 推断出的标签
+- 移除所有 `in:` labels
+- 移除 milestone
+- 移除全部 assignees
+- 发布取消评论，隐藏标记使用 `<!-- sync-issue:{task-id}:cancel -->`
+- 使用 `.agents/rules/issue-sync.md` 的 task.md 评论同步规则创建或更新 `<!-- sync-issue:{task-id}:task -->` 评论
+- 关闭 Issue：`gh issue close {issue-number} --reason "not planned"`
+
+取消评论至少包含：
+- 取消原因
+- 选定的 `status:` label
+
+### 7. 完成校验
+
+运行完成校验，确认任务归档和同步状态符合规范：
+
+```bash
+node .agents/scripts/validate-artifact.js gate cancel-task .agents/workspace/completed/{task-id} --format text
+```
+
+处理结果：
+- 退出码 0（全部通过）-> 继续到「告知用户」步骤
+- 退出码 1（校验失败）-> 根据输出修复问题后重新运行校验
+- 退出码 2（网络中断）-> 停止执行并告知用户需要人工介入
+
+将校验输出保留在回复中作为当次验证输出。没有当次校验输出，不得声明完成。
+
+### 8. 告知用户
+
+> 仅在校验通过后执行本步骤。
+
+> **重要**：以下「下一步」中列出的所有 TUI 命令格式必须完整输出，不要只展示当前 AI 代理对应的格式。
+
+输出格式：
+```
+任务 {task-id} 已取消并归档。
+
+取消原因：{reason}
+GitHub 标签：{status-label 或 skipped}
+归档路径：.agents/workspace/completed/{task-id}/
+
+下一步 - 查看归档任务：
+  - Claude Code / OpenCode：/check-task {task-id}
+  - Gemini CLI：/{{project}}:check-task {task-id}
+  - Codex CLI：$check-task {task-id}
+```
+
+## 完成检查清单
+
+- [ ] 已记录取消原因并更新 task.md
+- [ ] 已将任务目录移动到 `.agents/workspace/completed/`
+- [ ] 已在存在 Issue 时完成 GitHub 同步
+- [ ] 已运行 gate 校验并通过
+- [ ] 已向用户展示完整的下一步命令
+
+## 注意事项
+
+1. 取消任务不会新增 `cancelled` 状态值，而是复用 `completed`
+2. 必须通过 `cancelled_at` 和 `cancel_reason` 区分“取消”与“正常完成”
+3. 如果 Issue 关闭失败，不要宣称取消完成
+
+## 错误处理
+
+- 任务未找到：`Task {task-id} not found`
+- 任务已归档：提示任务已在 `completed/` 中
+- Issue 同步失败：保留本地归档结果，并告知用户需要人工补齐 GitHub 操作

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

@@ -0,0 +1,30 @@
+{
+  "skill": "cancel-task",
+  "checks": {
+    "task-meta": {
+      "required_fields": [
+        "id",
+        "type",
+        "workflow",
+        "status",
+        "created_at",
+        "updated_at",
+        "current_step",
+        "assigned_to",
+        "cancelled_at",
+        "cancel_reason"
+      ],
+      "expected_status": "completed",
+      "require_cancelled_at": true
+    },
+    "activity-log": {
+      "expected_action_pattern": "Cancelled",
+      "freshness_minutes": 30
+    },
+    "github-sync": {
+      "when": "issue_number_exists",
+      "expected_comment_marker": "<!-- sync-issue:{task-id}:cancel -->",
+      "verify_task_comment_content": true
+    }
+  }
+}

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

@@ -61,6 +61,7 @@ Update `.agents/workspace/active/{task-id}/task.md`:
 - `completed_at`: {current timestamp}
 - `updated_at`: {current timestamp}
 - Mark all workflow steps as complete
+- Verify and check off all items in `## Completion Checklist` (change `- [ ]` to `- [x]`)
 - **Append** to `## Activity Log` (do NOT overwrite previous entries):
   ```
   - {yyyy-MM-dd HH:mm:ss} — **Completed** by {agent} — Task archived to completed/

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

@@ -61,6 +61,7 @@ date "+%Y-%m-%d %H:%M:%S"
 - `completed_at`：{当前时间戳}
 - `updated_at`：{当前时间戳}
 - 标记所有工作流步骤为已完成
+- 逐项验证并勾选 `## 完成检查清单` 中的所有条目（将 `- [ ]` 改为 `- [x]`）
 - **追加**到 `## Activity Log`（不要覆盖之前的记录）：
   ```
   - {yyyy-MM-dd HH:mm:ss} — **Completed** by {agent} — Task archived to completed/

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

@@ -20,11 +20,16 @@
       "expected_action_pattern": "Completed",
       "freshness_minutes": 30
     },
+    "completion-checklist": {
+      "require_all_checked": true
+    },
     "github-sync": {
       "when": "issue_number_exists",
       "expected_comment_marker": "<!-- sync-issue:{task-id}:summary -->",
       "verify_task_comment_content": true,
-      "sync_checked_requirements": true
+      "sync_checked_requirements": true,
+      "verify_issue_type": true,
+      "verify_milestone": true
     }
   }
 }

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

@@ -27,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. 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.
+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. If task.md does not provide an explicit `milestone` field, infer it by following "Phase 1: `create-issue`" in `.agents/rules/milestone-inference.md`.
 
 ### 3. Build Issue Content
 
@@ -39,7 +39,7 @@ Detect `.github/ISSUE_TEMPLATE` files and decide whether to use a matched templa
 
 ### 4. Create the Issue
 
-Create the Issue with `gh issue create --title "{title}" --body "{body}" ...` and omit `--label` when nothing valid remains.
+Create the Issue with `gh issue create --title "{title}" --body "{body}" --assignee @me ...` and omit `--label` when nothing valid remains.
 
 If an Issue Type was selected, set it with:
 `gh api "repos/$repo/issues/{issue-number}" -X PATCH -f type="{issue-type}" --silent`

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

@@ -27,7 +27,7 @@ description: "从任务文件创建 GitHub Issue"
 
 ### 2. 提取任务信息
 
-从 task.md 提取标题、`## Description`、`## Requirements`、`type` 和 `milestone`。构造 Issue 标题：将 task.md 的 `type` 映射为 Conventional Commits type，推断 scope，拼接为 `cc_type(scope): task_title` 或 `cc_type: task_title`（scope 不确定时省略）。
+从 task.md 提取标题、`## Description`、`## Requirements`、`type` 和 `milestone`。构造 Issue 标题：将 task.md 的 `type` 映射为 Conventional Commits type，推断 scope，拼接为 `cc_type(scope): task_title` 或 `cc_type: task_title`（scope 不确定时省略）。如果 task.md 没有显式 `milestone` 字段，按 `.agents/rules/milestone-inference.md` 的「阶段 1：`create-issue`」推断。
 
 ### 3. 构建 Issue 内容
 
@@ -39,7 +39,7 @@ description: "从任务文件创建 GitHub Issue"
 
 ### 4. 创建 Issue
 
-使用 `gh issue create --title "{title}" --body "{body}" ...` 创建 Issue；如果没有有效 label，就省略 `--label`。
+使用 `gh issue create --title "{title}" --body "{body}" --assignee @me ...` 创建 Issue；如果没有有效 label，就省略 `--label`。
 
 如果已经确定了 Issue Type，则执行：
 `gh api "repos/$repo/issues/{issue-number}" -X PATCH -f type="{issue-type}" --silent`

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

@@ -21,7 +21,9 @@
     "github-sync": {
       "when": "issue_number_exists",
       "issue_must_exist": true,
-      "verify_task_comment_content": true
+      "verify_task_comment_content": true,
+      "verify_issue_type": true,
+      "verify_milestone": true
     }
   }
 }