@fitlab-ai/agent-infra 0.4.2 → 0.4.4

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/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/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/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/
@@ -82,22 +83,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:
 ```