@fitlab-ai/agent-infra 0.6.2 → 0.6.3

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

@@ -13,6 +13,20 @@ description: "Analyze a task and produce a requirements document"
 
 Version stamp rule: when creating or updating `task.md` frontmatter, read `.agents/rules/version-stamp.md` first and write or refresh `agent_infra_version`.
 
+## Step 0: State Check (pre-execution hard gate)
+
+After loading workflow / skill / rules instructions, and before any task-state judgment or user-visible conclusion, run the state check first. Reading instruction files does not count as an external-state action or conclusion.
+
+Run these commands and paste the raw output into both the user-facing reply and this round's `## State Check` section:
+
+```bash
+git status -s
+ls -la .agents/workspace/active/{task-id}/
+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.
+
 ## Steps
 
 ### 1. Verify Prerequisites
@@ -72,6 +86,10 @@ Create `.agents/workspace/active/{task-id}/{analysis-artifact}`.
 - **Analysis round**: Round {analysis-round}
 - **Artifact file**: `{analysis-artifact}`
 
+## State Check
+
+> Paste the raw Step 0 state-check command output; each command starts with `$ `.
+
 ## Requirement Source
 
 **Source type**: {User description / Issue / Code Scanning / Dependabot / Other}
@@ -118,6 +136,14 @@ Update `.agents/workspace/active/{task-id}/task.md`:
 - Record the analysis artifact for this round: `{analysis-artifact}` (Round `{analysis-round}`)
 - If the task template contains a `## Analysis` section, update it to link to `{analysis-artifact}`
 - Mark requirement-analysis as complete in workflow progress and include the actual round when the task template supports it
+- Before appending the workflow Activity Log entry, re-estimate `priority` based on the analysis findings (business impact, risks, dependencies, blockers). If the re-estimated value differs from the current value in `task.md`:
+  - Overwrite the `priority` field in frontmatter with the new value
+  - Prepend an Activity Log entry recording the transition (placed before the `Requirement Analysis (Round N)` entry):
+    ```
+    - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Analysis Re-estimate** by {agent} — priority {old} → {new} (rationale: {short basis grounded in this analysis})
+    ```
+  Both entries may share the same timestamp; ordering is conveyed by list position only.
+  If the re-estimated value matches the current value, skip the Re-estimate entry. The Flow A sync that follows reads the possibly updated frontmatter and propagates the new value to the Issue automatically.
 - **Append** to `## Activity Log` (do NOT overwrite previous entries):
   ```
   - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Requirement Analysis (Round {N})** by {agent} — Analysis completed → {analysis-artifact}

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

@@ -13,6 +13,20 @@ description: "分析任务并输出需求分析文档"
 
 版本戳规则：创建或更新 `task.md` frontmatter 时，先读取 `.agents/rules/version-stamp.md`，并写入或刷新 `agent_infra_version`。
 
+## 第 0 步：状态核对（执行前硬约束）
+
+在加载 workflow / skill / rules 指令之后、做任何任务状态判断或用户可见结论之前，必须先执行状态核对。指令类文件读取不算对外动作或结论。
+
+运行以下命令，并把原文粘贴到回复正文和本轮产物的 `## 状态核对` 段：
+
+```bash
+git status -s
+ls -la .agents/workspace/active/{task-id}/
+tail .agents/workspace/active/{task-id}/task.md
+```
+
+状态核对完成前，禁止任何关于外部状态的断言（例如“代码没变”“测试已通过”“没有其他引用”），包括思考阶段。本门禁只提供结构下限；逐条证据配对和真实性仍需按报告模板与审查要求核对。
+
 ## 执行步骤
 
 ### 1. 验证前置条件
@@ -72,6 +86,10 @@ description: "分析任务并输出需求分析文档"
 - **分析轮次**：Round {analysis-round}
 - **产物文件**：`{analysis-artifact}`
 
+## 状态核对
+
+> 粘贴第 0 步状态核对命令原文；每条命令以 `$ ` 开头。
+
 ## 需求来源
 
 **来源类型**：{用户描述 / Issue / Code Scanning / Dependabot / 其他}
@@ -118,6 +136,14 @@ date "+%Y-%m-%d %H:%M:%S%:z"
 - 记录本轮分析产物：`{analysis-artifact}`（Round `{analysis-round}`）
 - 如任务模板包含 `## 分析` 段落，更新为指向 `{analysis-artifact}` 的链接
 - 在工作流进度中标记 requirement-analysis 为已完成，并注明实际轮次（如果任务模板支持）
+- 在追加工作流 Activity Log 条目之前，基于分析结果（业务影响、风险、依赖、阻塞条件）重估 `priority`。若重估值与 `task.md` 当前值不一致：
+  - 用新值覆盖 frontmatter 的 `priority` 字段
+  - 在 `Requirement Analysis (Round N)` 条目之前追加一条转移记录：
+    ```
+    - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Analysis Re-estimate** by {agent} — priority {old} → {new} (rationale: {基于本轮分析的简短依据})
+    ```
+  两条条目可共用同一时间戳，顺序仅通过列表位置表达。
+  若重估值与当前值一致，跳过 Re-estimate 条目。后续 Flow A 同步会读取可能更新过的 frontmatter，并自动把新值同步到 Issue。
 - **追加**到 `## Activity Log`（不要覆盖之前的记录）：
   ```
   - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Requirement Analysis (Round {N})** by {agent} — Analysis completed → {analysis-artifact}

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

@@ -0,0 +1,51 @@
+{
+  "skill": "analyze-task",
+  "checks": {
+    "task-meta": {
+      "required_fields": [
+        "id",
+        "type",
+        "workflow",
+        "status",
+        "created_at",
+        "updated_at",
+        "agent_infra_version",
+        "current_step",
+        "assigned_to"
+      ],
+      "expected_step": "requirement-analysis"
+    },
+    "artifact": {
+      "file_pattern": "analysis.md|analysis-r{N}.md",
+      "required_sections": [
+        "Requirement Source",
+        "Requirement Understanding",
+        "Related Files",
+        "Impact Assessment",
+        "Technical Risks",
+        "Effort and Complexity Assessment",
+        "State Check"
+      ],
+      "freshness_minutes": 30,
+      "required_patterns": [
+        "^\\$ "
+      ]
+    },
+    "activity-log": {
+      "expected_action_pattern": "Requirement Analysis \\(Round \\d+\\)",
+      "freshness_minutes": 30
+    },
+    "platform-sync": {
+      "when": "issue_number_exists",
+      "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_issue_type": true,
+      "verify_issue_fields": false,
+      "verify_milestone": true,
+      "expected_status_label_key": "pendingDesignWork",
+      "expected_comment_marker_key": "artifact"
+    }
+  }
+}

package/templates/.agents/skills/analyze-task/config/{verify.json → verify.zh-CN.json}

@@ -23,9 +23,13 @@
         "相关文件",
         "影响评估",
         "技术风险",
-        "工作量和复杂度评估"
+        "工作量和复杂度评估",
+        "状态核对"
       ],
-      "freshness_minutes": 30
+      "freshness_minutes": 30,
+      "required_patterns": [
+        "^\\$ "
+      ]
     },
     "activity-log": {
       "expected_action_pattern": "Requirement Analysis \\(Round \\d+\\)",

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

@@ -12,6 +12,20 @@ description: "Mark a task as completed and archive it"
 
 Version stamp rule: when creating or updating `task.md` frontmatter, read `.agents/rules/version-stamp.md` first and write or refresh `agent_infra_version`.
 
+## Step 0: State Check (pre-execution hard gate)
+
+After loading workflow / skill / rules instructions, and before any task-state judgment or user-visible conclusion, run the state check first. Reading instruction files does not count as an external-state action or conclusion.
+
+Run these commands and paste the raw output into both the user-facing reply and this round's `## State Check` section:
+
+```bash
+git status -s
+ls -la .agents/workspace/active/{task-id}/
+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.
+
 ## Steps
 
 ### 1. Verify Task Exists
@@ -64,6 +78,7 @@ Update `.agents/workspace/active/{task-id}/task.md`:
 - `completed_at`: {current timestamp}
 - `updated_at`: {current timestamp}
 - `agent_infra_version`: value from `.agents/rules/version-stamp.md`
+- Add or update the `## State Check` section with the raw Step 0 audit command output, including `$ ` prompt lines, before `## Activity Log`
 - 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):

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

@@ -12,6 +12,20 @@ description: "标记任务完成并归档"
 
 版本戳规则：创建或更新 `task.md` frontmatter 时，先读取 `.agents/rules/version-stamp.md`，并写入或刷新 `agent_infra_version`。
 
+## 第 0 步：状态核对（执行前硬约束）
+
+在加载 workflow / skill / rules 指令之后、做任何任务状态判断或用户可见结论之前，必须先执行状态核对。指令类文件读取不算对外动作或结论。
+
+运行以下命令，并把原文粘贴到回复正文和本轮产物的 `## 状态核对` 段：
+
+```bash
+git status -s
+ls -la .agents/workspace/active/{task-id}/
+tail .agents/workspace/active/{task-id}/task.md
+```
+
+状态核对完成前，禁止任何关于外部状态的断言（例如“代码没变”“测试已通过”“没有其他引用”），包括思考阶段。本门禁只提供结构下限；逐条证据配对和真实性仍需按报告模板与审查要求核对。
+
 ## 执行步骤
 
 ### 1. 验证任务存在
@@ -64,6 +78,7 @@ date "+%Y-%m-%d %H:%M:%S%:z"
 - `completed_at`：{当前时间戳}
 - `updated_at`：{当前时间戳}
 - `agent_infra_version`：按 `.agents/rules/version-stamp.md` 取值
+- 新增或更新 `## 状态核对` 段，粘贴第 0 步审计命令原文（含 `$ ` 前缀行），放在 `## 活动日志` 之前
 - 标记所有工作流步骤为已完成
 - 逐项验证并勾选 `## 完成检查清单` 中的所有条目（将 `- [ ]` 改为 `- [x]`）
 - **追加**到 `## Activity Log`（不要覆盖之前的记录）：

package/templates/.agents/skills/complete-task/config/{verify.json → verify.en.json}

@@ -33,6 +33,16 @@
       "verify_issue_fields": false,
       "verify_milestone": true,
       "expected_comment_marker_key": "summary"
+    },
+    "artifact": {
+      "file_pattern": "task.md",
+      "required_sections": [
+        "State Check"
+      ],
+      "required_patterns": [
+        "^\\$ "
+      ],
+      "freshness_minutes": 30
     }
   }
 }

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

@@ -0,0 +1,48 @@
+{
+  "skill": "complete-task",
+  "checks": {
+    "task-meta": {
+      "required_fields": [
+        "id",
+        "type",
+        "workflow",
+        "status",
+        "created_at",
+        "updated_at",
+        "agent_infra_version",
+        "current_step",
+        "assigned_to",
+        "completed_at"
+      ],
+      "expected_status": "completed",
+      "require_completed_at": true
+    },
+    "activity-log": {
+      "expected_action_pattern": "Completed",
+      "freshness_minutes": 30
+    },
+    "completion-checklist": {
+      "require_all_checked": true
+    },
+    "platform-sync": {
+      "when": "issue_number_exists",
+      "expected_comment_marker": "<!-- sync-issue:{task-id}:summary -->",
+      "verify_task_comment_content": true,
+      "sync_checked_requirements": true,
+      "verify_issue_type": true,
+      "verify_issue_fields": false,
+      "verify_milestone": true,
+      "expected_comment_marker_key": "summary"
+    },
+    "artifact": {
+      "file_pattern": "task.md",
+      "required_sections": [
+        "状态核对"
+      ],
+      "required_patterns": [
+        "^\\$ "
+      ],
+      "freshness_minutes": 30
+    }
+  }
+}

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

@@ -27,6 +27,20 @@ Before implementing, stop if any of these thoughts appear. They are violations:
 | "This plan is flawed, so I will improve it as I go." | Deviations from `{plan-artifact}` must be recorded in the report; if the direction is questionable, stop and confirm instead of changing it silently. |
 | "The tests passed, so I can commit this too." | This skill never runs `git add` or `git commit`; committing is a separate step explicitly requested by the user. |
 
+## Step 0: State Check (pre-execution hard gate)
+
+After loading workflow / skill / rules instructions, and before any task-state judgment or user-visible conclusion, run the state check first. Reading instruction files does not count as an external-state action or conclusion.
+
+Run these commands and paste the raw output into both the user-facing reply and this round's `## State Check` section:
+
+```bash
+git status -s
+ls -la .agents/workspace/active/{task-id}/
+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.
+
 ## Steps
 
 ### 1. Verify Prerequisites

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

@@ -27,6 +27,20 @@ description: "根据技术方案实施任务并输出报告"
 | 「方案这里不合理，顺手改更好」 | 偏离 `{plan-artifact}` 必须在报告中记录原因；有异议先停下确认，不擅自改方向。 |
 | 「测试过了，顺便提交一下」 | 本技能绝不执行 `git add`/`git commit`，提交是用户显式发起的独立步骤。 |
 
+## 第 0 步：状态核对（执行前硬约束）
+
+在加载 workflow / skill / rules 指令之后、做任何任务状态判断或用户可见结论之前，必须先执行状态核对。指令类文件读取不算对外动作或结论。
+
+运行以下命令，并把原文粘贴到回复正文和本轮产物的 `## 状态核对` 段：
+
+```bash
+git status -s
+ls -la .agents/workspace/active/{task-id}/
+tail .agents/workspace/active/{task-id}/task.md
+```
+
+状态核对完成前，禁止任何关于外部状态的断言（例如“代码没变”“测试已通过”“没有其他引用”），包括思考阶段。本门禁只提供结构下限；逐条证据配对和真实性仍需按报告模板与审查要求核对。
+
 ## 执行步骤
 
 ### 1. 验证前置条件

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

@@ -0,0 +1,51 @@
+{
+  "skill": "implement-task",
+  "checks": {
+    "task-meta": {
+      "required_fields": [
+        "id",
+        "type",
+        "workflow",
+        "status",
+        "created_at",
+        "updated_at",
+        "agent_infra_version",
+        "current_step",
+        "assigned_to"
+      ],
+      "expected_step": "implementation"
+    },
+    "artifact": {
+      "file_pattern": "implementation.md|implementation-r{N}.md",
+      "required_sections": [
+        "Modified Files",
+        "Key Code Explanation",
+        "Test Results",
+        "Differences from Plan",
+        "Items for Review",
+        "State Check",
+        "Evidence"
+      ],
+      "freshness_minutes": 30,
+      "required_patterns": [
+        "^\\$ "
+      ]
+    },
+    "activity-log": {
+      "expected_action_pattern": "Implementation \\(Round \\d+\\)",
+      "freshness_minutes": 30
+    },
+    "platform-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,
+      "verify_issue_type": true,
+      "verify_issue_fields": false,
+      "verify_milestone": true,
+      "expected_status_label_key": "inProgress",
+      "expected_comment_marker_key": "artifact"
+    }
+  }
+}

package/templates/.agents/skills/implement-task/config/{verify.json → verify.zh-CN.json}

@@ -22,9 +22,14 @@
         "关键代码说明",
         "测试结果",
         "与方案的差异",
-        "供审查关注的内容"
+        "供审查关注的内容",
+        "状态核对",
+        "证据原文"
       ],
-      "freshness_minutes": 30
+      "freshness_minutes": 30,
+      "required_patterns": [
+        "^\\$ "
+      ]
     },
     "activity-log": {
       "expected_action_pattern": "Implementation \\(Round \\d+\\)",

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

@@ -10,6 +10,10 @@ Use this structure when creating `implementation.md` or `implementation-r{N}.md`
 - **Implementation Round**: Round {implementation-round}
 - **Artifact File**: `{implementation-artifact}`
 
+## State Check
+
+> Paste the raw state-check command output; each command starts with `$ `.
+
 ## Modified Files
 
 ### New Files
@@ -43,6 +47,17 @@ Use this structure when creating `implementation.md` or `implementation-r{N}.md`
 {test-run-output}
 ```
 
+
+## Evidence
+
+> Pair each "I verified X" claim with the corresponding raw tool output; the gate only checks that this section exists and at least one `$ ` line is present.
+
+- Claim: {verified claim}
+```text
+$ {command}
+{raw output}
+```
+
 ## Differences from Plan
 
 {describe any deviation from the approved plan}

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

@@ -10,6 +10,10 @@
 - **实现轮次**: Round {implementation-round}
 - **产物文件**: `{implementation-artifact}`
 
+## 状态核对
+
+> 粘贴状态核对命令原文；每条命令以 `$ ` 开头。
+
 ## 变更文件
 
 ### 新建文件
@@ -43,6 +47,17 @@
 {test-run-output}
 ```
 
+
+## 证据原文
+
+> 每条“我验证了 X”断言都要配对对应 tool output 原文；gate 仅校验本段存在和至少一行 `$ `。
+
+- 断言：{verified claim}
+```text
+$ {command}
+{raw output}
+```
+
 ## 与方案的差异
 
 {describe any deviation from the approved plan}

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

@@ -13,6 +13,20 @@ description: "Design a technical plan for a 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`.
 
+## Step 0: State Check (pre-execution hard gate)
+
+After loading workflow / skill / rules instructions, and before any task-state judgment or user-visible conclusion, run the state check first. Reading instruction files does not count as an external-state action or conclusion.
+
+Run these commands and paste the raw output into both the user-facing reply and this round's `## State Check` section:
+
+```bash
+git status -s
+ls -la .agents/workspace/active/{task-id}/
+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.
+
 ## Steps
 
 ### 1. Verify Prerequisites
@@ -95,6 +109,14 @@ Update `.agents/workspace/active/{task-id}/task.md`:
 - Record the plan artifact for this round: `{plan-artifact}` (Round `{plan-round}`)
 - If the task template contains a `## Design` section, update it to link to `{plan-artifact}`
 - Mark technical-design as complete in workflow progress and include the actual round when the task template supports it
+- Before appending the workflow Activity Log entry, re-estimate `effort` based on the technical plan (number of implementation steps, files touched, test matrix scope, integration surface). If the re-estimated value differs from the current value in `task.md`:
+  - Overwrite the `effort` field in frontmatter with the new value
+  - Prepend an Activity Log entry recording the transition (placed before the `Technical Design (Round N)` entry):
+    ```
+    - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Plan Re-estimate** by {agent} — effort {old} → {new} (rationale: {short basis grounded in this plan})
+    ```
+  Both entries may share the same timestamp; ordering is conveyed by list position only.
+  If the re-estimated value matches the current value, skip the Re-estimate entry. The Flow A sync that follows reads the possibly updated frontmatter and propagates the new value to the Issue automatically.
 - **Append** to `## Activity Log` (do NOT overwrite previous entries):
   ```
   - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Technical Design (Round {N})** by {agent} — Plan completed, awaiting human review → {artifact-filename}

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

@@ -13,6 +13,20 @@ description: "为任务设计技术方案和实施计划"
 
 版本戳规则：创建或更新 `task.md` frontmatter 时，先读取 `.agents/rules/version-stamp.md`，并写入或刷新 `agent_infra_version`。
 
+## 第 0 步：状态核对（执行前硬约束）
+
+在加载 workflow / skill / rules 指令之后、做任何任务状态判断或用户可见结论之前，必须先执行状态核对。指令类文件读取不算对外动作或结论。
+
+运行以下命令，并把原文粘贴到回复正文和本轮产物的 `## 状态核对` 段：
+
+```bash
+git status -s
+ls -la .agents/workspace/active/{task-id}/
+tail .agents/workspace/active/{task-id}/task.md
+```
+
+状态核对完成前，禁止任何关于外部状态的断言（例如“代码没变”“测试已通过”“没有其他引用”），包括思考阶段。本门禁只提供结构下限；逐条证据配对和真实性仍需按报告模板与审查要求核对。
+
 ## 执行步骤
 
 ### 1. 验证前置条件
@@ -95,6 +109,14 @@ date "+%Y-%m-%d %H:%M:%S%:z"
 - 记录本轮方案产物：`{plan-artifact}`（Round `{plan-round}`）
 - 如任务模板包含 `## 设计` 段落，更新为指向 `{plan-artifact}` 的链接
 - 在工作流进度中标记 technical-design 为已完成，并注明实际轮次（如果任务模板支持）
+- 在追加工作流 Activity Log 条目之前，基于技术方案（实施步骤数、涉及文件、测试矩阵范围、集成面）重估 `effort`。若重估值与 `task.md` 当前值不一致：
+  - 用新值覆盖 frontmatter 的 `effort` 字段
+  - 在 `Technical Design (Round N)` 条目之前追加一条转移记录：
+    ```
+    - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Plan Re-estimate** by {agent} — effort {old} → {new} (rationale: {基于本轮方案的简短依据})
+    ```
+  两条条目可共用同一时间戳，顺序仅通过列表位置表达。
+  若重估值与当前值一致，跳过 Re-estimate 条目。后续 Flow A 同步会读取可能更新过的 frontmatter，并自动把新值同步到 Issue。
 - **追加**到 `## Activity Log`（不要覆盖之前的记录）：
   ```
   - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Technical Design (Round {N})** by {agent} — Plan completed, awaiting human review → {artifact-filename}

package/templates/.agents/skills/plan-task/config/verify.en.json

@@ -0,0 +1,52 @@
+{
+  "skill": "plan-task",
+  "checks": {
+    "task-meta": {
+      "required_fields": [
+        "id",
+        "type",
+        "workflow",
+        "status",
+        "created_at",
+        "updated_at",
+        "agent_infra_version",
+        "current_step",
+        "assigned_to"
+      ],
+      "expected_step": "technical-design"
+    },
+    "artifact": {
+      "file_pattern": "plan.md|plan-r{N}.md",
+      "required_sections": [
+        "Problem Understanding",
+        "Constraints",
+        "Option Comparison",
+        "Technical Approach",
+        "Implementation Steps",
+        "File List",
+        "Verification Strategy",
+        "State Check"
+      ],
+      "freshness_minutes": 30,
+      "required_patterns": [
+        "^\\$ "
+      ]
+    },
+    "activity-log": {
+      "expected_action_pattern": "Technical Design \\(Round \\d+\\)",
+      "freshness_minutes": 30
+    },
+    "platform-sync": {
+      "when": "issue_number_exists",
+      "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_issue_type": true,
+      "verify_issue_fields": false,
+      "verify_milestone": true,
+      "expected_status_label_key": "pendingDesignWork",
+      "expected_comment_marker_key": "artifact"
+    }
+  }
+}

package/templates/.agents/skills/plan-task/config/{verify.json → verify.zh-CN.json}

@@ -24,9 +24,13 @@
         "技术方法",
         "实施步骤",
         "文件清单",
-        "验证策略"
+        "验证策略",
+        "状态核对"
       ],
-      "freshness_minutes": 30
+      "freshness_minutes": 30,
+      "required_patterns": [
+        "^\\$ "
+      ]
     },
     "activity-log": {
       "expected_action_pattern": "Technical Design \\(Round \\d+\\)",

package/templates/.agents/skills/post-release/SKILL.en.md

@@ -54,6 +54,7 @@ git status --short
 <!-- TODO: Add project-specific follow-up tasks such as demo capture, docs publishing, or downstream notifications -->
 
 - Examples: record a terminal demo, refresh a docs site, notify downstream teams, update release dashboards
+- If a task here displays or captures the just-released version (e.g., recording a CLI demo), move it **before** Step 3 — otherwise it will reflect the next development version, not the release
 - If there are no extra tasks, remove this step in the project-specific copy
 
 ### 6. Create the Follow-up Commit

package/templates/.agents/skills/post-release/SKILL.zh-CN.md

@@ -54,6 +54,7 @@ git status --short
 <!-- TODO: 添加项目特定的发布后任务，例如录制演示、发布文档站或通知下游 -->
 
 - 示例：录制终端演示、刷新文档站、通知下游团队、更新发布面板
+- 如果这一步里的任务需要显示或捕获刚发布的版本号（例如录制 CLI 演示），把它挪到**第 3 步「准备下一个开发版本」之前**——否则会反映下一个开发版本号，而不是 released 版本号
 - 如果没有额外任务，请在项目特化版本中删除此步骤
 
 ### 6. 创建后处理提交

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

@@ -24,6 +24,20 @@ Version stamp rule: when creating or updating `task.md` frontmatter, read `.agen
 | "I can clean up nearby code while I am here." | Scope is limited to review findings; changes outside that scope are out of bounds. |
 | "Clearing env-blocked items makes the report look better." | env-blocked findings are outside the repair scope; preserve and label them truthfully, and never use no-op edits to pad the fix count. |
 
+## Step 0: State Check (pre-execution hard gate)
+
+After loading workflow / skill / rules instructions, and before any task-state judgment or user-visible conclusion, run the state check first. Reading instruction files does not count as an external-state action or conclusion.
+
+Run these commands and paste the raw output into both the user-facing reply and this round's `## State Check` section:
+
+```bash
+git status -s
+ls -la .agents/workspace/active/{task-id}/
+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.
+
 ## Steps
 
 ### 1. Verify Prerequisites