@fitlab-ai/agent-infra 0.3.2 → 0.4.0

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

@@ -55,7 +55,7 @@ Get the current timestamp:
 date +%Y%m%d-%H%M%S
 ```
 
-- Create the task directory: `.agent-workspace/active/TASK-{yyyyMMdd-HHmmss}/`
+- Create the task directory: `.agents/workspace/active/TASK-{yyyyMMdd-HHmmss}/`
 - Use the `.agents/templates/task.md` template to create the task file: `task.md`
 
 **Important**:
@@ -86,7 +86,7 @@ Get the current time:
 date "+%Y-%m-%d %H:%M:%S"
 ```
 
-Update `.agent-workspace/active/{task-id}/task.md`:
+Update `.agents/workspace/active/{task-id}/task.md`:
 - `current_step`: requirement-analysis
 - `assigned_to`: {current AI agent}
 - `updated_at`: {current time}
@@ -110,7 +110,7 @@ Task information:
 - Workflow: {workflow}
 
 Output file:
-- Task file: .agent-workspace/active/{task-id}/task.md
+- Task file: .agents/workspace/active/{task-id}/task.md
 
 Next step - run requirements analysis:
   - Claude Code / OpenCode: /analyze-task {task-id}
@@ -120,7 +120,7 @@ Next step - run requirements analysis:
 
 ## Completion Checklist
 
-- [ ] Created the task file `.agent-workspace/active/{task-id}/task.md`
+- [ ] Created the task file `.agents/workspace/active/{task-id}/task.md`
 - [ ] Updated `current_step` to requirement-analysis in task.md
 - [ ] Updated `updated_at` to the current time in task.md
 - [ ] Updated `assigned_to` in task.md

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

@@ -54,7 +54,7 @@ description: >
 date +%Y%m%d-%H%M%S
 ```
 
-- 创建任务目录：`.agent-workspace/active/TASK-{yyyyMMdd-HHmmss}/`
+- 创建任务目录：`.agents/workspace/active/TASK-{yyyyMMdd-HHmmss}/`
 - 使用 `.agents/templates/task.md` 模板创建任务文件：`task.md`
 
 **重要**：
@@ -85,7 +85,7 @@ assigned_to: {当前 AI 代理}
 date "+%Y-%m-%d %H:%M:%S"
 ```
 
-更新 `.agent-workspace/active/{task-id}/task.md`：
+更新 `.agents/workspace/active/{task-id}/task.md`：
 - `current_step`：requirement-analysis
 - `assigned_to`：{当前 AI 代理}
 - `updated_at`：{当前时间}
@@ -109,7 +109,7 @@ date "+%Y-%m-%d %H:%M:%S"
 - 工作流：{workflow}
 
 产出文件：
-- 任务文件：.agent-workspace/active/{task-id}/task.md
+- 任务文件：.agents/workspace/active/{task-id}/task.md
 
 下一步 - 执行需求分析：
   - Claude Code / OpenCode：/analyze-task {task-id}
@@ -119,7 +119,7 @@ date "+%Y-%m-%d %H:%M:%S"
 
 ## 完成检查清单
 
-- [ ] 创建了任务文件 `.agent-workspace/active/{task-id}/task.md`
+- [ ] 创建了任务文件 `.agents/workspace/active/{task-id}/task.md`
 - [ ] 更新了 task.md 中的 `current_step` 为 requirement-analysis
 - [ ] 更新了 task.md 中的 `updated_at` 为当前时间
 - [ ] 更新了 task.md 中的 `assigned_to`

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

@@ -21,7 +21,7 @@ description: >
 ### 1. Verify Prerequisites
 
 Check required files:
-- `.agent-workspace/active/{task-id}/task.md` - Task file
+- `.agents/workspace/active/{task-id}/task.md` - Task file
 - At least one technical plan artifact: `plan.md` or `plan-r{N}.md`
 
 Note: `{task-id}` format is `TASK-{yyyyMMdd-HHmmss}`, e.g. `TASK-20260306-143022`
@@ -30,10 +30,10 @@ If either file is missing, prompt the user to complete the prerequisite step fir
 
 ### 2. Determine the Input Plan and Implementation Round
 
-Scan `.agent-workspace/active/{task-id}/` for technical plan files (`plan.md`, `plan-r{N}.md`):
+Scan `.agents/workspace/active/{task-id}/` for technical plan files (`plan.md`, `plan-r{N}.md`):
 - Read the highest-round plan file and record it as `{plan-artifact}`
 
-Scan `.agent-workspace/active/{task-id}/` for implementation report files:
+Scan `.agents/workspace/active/{task-id}/` for implementation report files:
 - If neither `implementation.md` nor `implementation-r*.md` exists -> this is Round 1 and must create `implementation.md`
 - If `implementation.md` exists and no `implementation-r*.md` exists -> this is Round 2 and must create `implementation-r2.md`
 - If `implementation-r{N}.md` exists -> this is Round N+1 and must create `implementation-r{N+1}.md`
@@ -93,7 +93,7 @@ Proceed to Steps 6, 7, and 8 only after the full test suite passes.
 
 ### 6. Output Implementation Report
 
-Create `.agent-workspace/active/{task-id}/{implementation-artifact}`.
+Create `.agents/workspace/active/{task-id}/{implementation-artifact}`.
 
 Requirements:
 - Do not overwrite any existing implementation report
@@ -108,7 +108,7 @@ Get the current time:
 date "+%Y-%m-%d %H:%M:%S"
 ```
 
-Update `.agent-workspace/active/{task-id}/task.md`:
+Update `.agents/workspace/active/{task-id}/task.md`:
 - `current_step`: implementation
 - `assigned_to`: {current AI agent}
 - `updated_at`: {current time}
@@ -133,7 +133,7 @@ Summary:
 - Tests passed: {count}/{total}
 
 Output file:
-- Implementation report: .agent-workspace/active/{task-id}/{implementation-artifact} (Round {implementation-round})
+- Implementation report: .agents/workspace/active/{task-id}/{implementation-artifact} (Round {implementation-round})
 
 Next step - code review:
   - Claude Code / OpenCode: /review-task {task-id}
@@ -204,7 +204,7 @@ Next step - code review:
 ## Completion Checklist
 
 - [ ] Completed all code implementation
-- [ ] Created implementation report `.agent-workspace/active/{task-id}/{implementation-artifact}`
+- [ ] Created implementation report `.agents/workspace/active/{task-id}/{implementation-artifact}`
 - [ ] All tests pass
 - [ ] Updated `current_step` to implementation in task.md
 - [ ] Updated `updated_at` to current time in task.md
@@ -221,7 +221,7 @@ After completing the checklist, **stop**. Do not auto-commit. Wait for code revi
 
 1. **Prerequisites**: Must have a reviewed technical plan (`plan.md` or `plan-r{N}.md` exists and is approved)
 2. **No auto-commit**: Do NOT execute `git commit` or `git add` automatically. Remind the user to commit manually
-3. **Test requirement**: All new code must have unit tests; test coverage must not decrease
+3. **Test requirement**: All new code must have unit tests; test coverage must not decrease. When removing a feature, delete the test fixtures and assertions that existed solely for that feature — do not mechanically flip assertions; every assertion must verify meaningful business logic, not merely confirm that data passes through unchanged
 4. **Code quality**: Follow project coding standards
 5. **Plan deviation**: If you need to deviate from the plan, document the reason in the implementation report
 6. **Versioning rule**: First-round implementation uses `implementation.md`; later re-implementations use `implementation-r{N}.md`

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

@@ -19,7 +19,7 @@ description: >
 ### 1. 验证前置条件
 
 检查必要文件：
-- `.agent-workspace/active/{task-id}/task.md` - 任务文件
+- `.agents/workspace/active/{task-id}/task.md` - 任务文件
 - 至少一个技术方案产物：`plan.md` 或 `plan-r{N}.md`
 
 注意：`{task-id}` 格式为 `TASK-{yyyyMMdd-HHmmss}`，例如 `TASK-20260306-143022`
@@ -28,10 +28,10 @@ description: >
 
 ### 2. 确定输入方案与实现轮次
 
-扫描 `.agent-workspace/active/{task-id}/` 目录中的技术方案文件（`plan.md`、`plan-r{N}.md`）：
+扫描 `.agents/workspace/active/{task-id}/` 目录中的技术方案文件（`plan.md`、`plan-r{N}.md`）：
 - 读取最高轮次的方案文件，记为 `{plan-artifact}`
 
-扫描 `.agent-workspace/active/{task-id}/` 目录中的实现报告文件：
+扫描 `.agents/workspace/active/{task-id}/` 目录中的实现报告文件：
 - 如果不存在 `implementation.md` 且不存在 `implementation-r*.md` → 本轮为第 1 轮，产出 `implementation.md`
 - 如果存在 `implementation.md` 且不存在 `implementation-r*.md` → 本轮为第 2 轮，产出 `implementation-r2.md`
 - 如果存在 `implementation-r{N}.md` → 本轮为第 N+1 轮，产出 `implementation-r{N+1}.md`
@@ -91,7 +91,7 @@ description: >
 
 ### 6. 输出实现报告
 
-创建 `.agent-workspace/active/{task-id}/{implementation-artifact}`。
+创建 `.agents/workspace/active/{task-id}/{implementation-artifact}`。
 
 要求：
 - 不要覆盖已有的实现报告
@@ -106,7 +106,7 @@ description: >
 date "+%Y-%m-%d %H:%M:%S"
 ```
 
-更新 `.agent-workspace/active/{task-id}/task.md`：
+更新 `.agents/workspace/active/{task-id}/task.md`：
 - `current_step`：implementation
 - `assigned_to`：{当前 AI 代理}
 - `updated_at`：{当前时间}
@@ -131,7 +131,7 @@ date "+%Y-%m-%d %H:%M:%S"
 - 测试通过：{数量}/{总数}
 
 产出文件：
-- 实现报告：.agent-workspace/active/{task-id}/{implementation-artifact}（Round {implementation-round}）
+- 实现报告：.agents/workspace/active/{task-id}/{implementation-artifact}（Round {implementation-round}）
 
 下一步 - 代码审查：
   - Claude Code / OpenCode：/review-task {task-id}
@@ -202,7 +202,7 @@ date "+%Y-%m-%d %H:%M:%S"
 ## 完成检查清单
 
 - [ ] 完成了所有代码实现
-- [ ] 创建了实现报告 `.agent-workspace/active/{task-id}/{implementation-artifact}`
+- [ ] 创建了实现报告 `.agents/workspace/active/{task-id}/{implementation-artifact}`
 - [ ] 所有测试通过
 - [ ] 更新了 task.md 中的 `current_step` 为 implementation
 - [ ] 更新了 task.md 中的 `updated_at` 为当前时间
@@ -219,7 +219,7 @@ date "+%Y-%m-%d %H:%M:%S"
 
 1. **前置条件**：必须有已审查的技术方案（`plan.md` 或 `plan-r{N}.md` 存在且已获批准）
 2. **禁止自动提交**：不要自动执行 `git commit` 或 `git add`。提醒用户手动提交
-3. **测试要求**：所有新代码必须有单元测试；测试覆盖率不得下降
+3. **测试要求**：所有新代码必须有单元测试；测试覆盖率不得下降。删除功能时，必须同时删除为该功能而存在的测试 fixture 和断言，不要机械地翻转断言方向；每条断言都应验证有意义的业务逻辑，仅确认数据原样通过的断言不构成有效测试
 4. **代码质量**：遵循项目编码规范
 5. **计划偏离**：如果需要偏离计划，在实现报告中记录原因
 6. **版本化规则**：首轮实现使用 `implementation.md`；后续重实现使用 `implementation-r{N}.md`

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

@@ -36,7 +36,7 @@ Extract key information:
 
 Check whether a task for this alert already exists. If not, create one:
 
-Directory: `.agent-workspace/active/TASK-{yyyyMMdd-HHmmss}/`
+Directory: `.agents/workspace/active/TASK-{yyyyMMdd-HHmmss}/`
 
 Task metadata:
 ```yaml

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

@@ -35,7 +35,7 @@ gh api repos/{owner}/{repo}/code-scanning/alerts/<alert-number>
 
 检查是否已存在该告警的任务。如果不存在，创建：
 
-目录：`.agent-workspace/active/TASK-{yyyyMMdd-HHmmss}/`
+目录：`.agents/workspace/active/TASK-{yyyyMMdd-HHmmss}/`
 
 任务元数据：
 ```yaml

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

@@ -33,11 +33,11 @@ Extract key information:
 
 ### 2. Create the Task Directory and File
 
-Check whether `.agent-workspace/active/` already has a task for this alert.
+Check whether `.agents/workspace/active/` already has a task for this alert.
 - If found, ask the user whether to re-import
 - If not found, create a new task
 
-Create directory: `.agent-workspace/active/TASK-{yyyyMMdd-HHmmss}/`
+Create directory: `.agents/workspace/active/TASK-{yyyyMMdd-HHmmss}/`
 
 Task metadata must include:
 ```yaml
@@ -78,7 +78,7 @@ Task information:
 - Task ID: {task-id}
 
 Output file:
-- Task file: .agent-workspace/active/{task-id}/task.md
+- Task file: .agents/workspace/active/{task-id}/task.md
 
 Next step:
   - Claude Code / OpenCode: /analyze-task {task-id}

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

@@ -32,11 +32,11 @@ gh api repos/{owner}/{repo}/dependabot/alerts/<alert-number>
 
 ### 2. 创建任务目录和文件
 
-检查 `.agent-workspace/active/` 中是否已存在该告警的任务。
+检查 `.agents/workspace/active/` 中是否已存在该告警的任务。
 - 如果找到，询问用户是否重新导入
 - 如果未找到，创建新任务
 
-创建目录：`.agent-workspace/active/TASK-{yyyyMMdd-HHmmss}/`
+创建目录：`.agents/workspace/active/TASK-{yyyyMMdd-HHmmss}/`
 
 任务元数据需包含：
 ```yaml
@@ -77,7 +77,7 @@ date "+%Y-%m-%d %H:%M:%S"
 - 任务 ID：{task-id}
 
 产出文件：
-- 任务文件：.agent-workspace/active/{task-id}/task.md
+- 任务文件：.agents/workspace/active/{task-id}/task.md
 
 下一步：
   - Claude Code / OpenCode：/analyze-task {task-id}

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

@@ -27,7 +27,7 @@ Extract: issue number, title, description, and labels.
 
 ### 2. Check for an Existing Task
 
-Search `.agent-workspace/active/` for an existing task linked to this Issue.
+Search `.agents/workspace/active/` for an existing task linked to this Issue.
 - If found, ask the user whether to re-import or continue with the existing task
 - If not found, create a new task
 
@@ -37,7 +37,7 @@ Search `.agent-workspace/active/` for an existing task linked to this Issue.
 date +%Y%m%d-%H%M%S
 ```
 
-- Create the directory: `.agent-workspace/active/TASK-{yyyyMMdd-HHmmss}/`
+- Create the directory: `.agents/workspace/active/TASK-{yyyyMMdd-HHmmss}/`
 - Use the `.agents/templates/task.md` template to create `task.md`
 
 Task metadata:
@@ -62,7 +62,7 @@ Get the current time:
 date "+%Y-%m-%d %H:%M:%S"
 ```
 
-Update `.agent-workspace/active/{task-id}/task.md`:
+Update `.agents/workspace/active/{task-id}/task.md`:
 - `current_step`: requirement-analysis
 - `assigned_to`: {current AI agent}
 - `updated_at`: {current time}
@@ -84,7 +84,7 @@ Task information:
 - Workflow: {workflow}
 
 Output file:
-- Task file: .agent-workspace/active/{task-id}/task.md
+- Task file: .agents/workspace/active/{task-id}/task.md
 
 Next step - run requirements analysis:
   - Claude Code / OpenCode: /analyze-task {task-id}
@@ -94,7 +94,7 @@ Next step - run requirements analysis:
 
 ## Completion Checklist
 
-- [ ] Created the task file `.agent-workspace/active/{task-id}/task.md`
+- [ ] Created the task file `.agents/workspace/active/{task-id}/task.md`
 - [ ] Recorded `issue_number` in task.md
 - [ ] Updated `current_step` to requirement-analysis
 - [ ] Updated `updated_at` to the current time

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

@@ -27,7 +27,7 @@ gh issue view <issue-number> --json number,title,body,labels
 
 ### 2. 检查已有任务
 
-搜索 `.agent-workspace/active/` 中是否已有链接到此 Issue 的任务。
+搜索 `.agents/workspace/active/` 中是否已有链接到此 Issue 的任务。
 - 如果找到，询问用户是重新导入还是继续使用现有任务
 - 如果未找到，创建新任务
 
@@ -37,7 +37,7 @@ gh issue view <issue-number> --json number,title,body,labels
 date +%Y%m%d-%H%M%S
 ```
 
-- 创建目录：`.agent-workspace/active/TASK-{yyyyMMdd-HHmmss}/`
+- 创建目录：`.agents/workspace/active/TASK-{yyyyMMdd-HHmmss}/`
 - 使用 `.agents/templates/task.md` 模板创建 `task.md`
 
 任务元数据：
@@ -62,7 +62,7 @@ assigned_to: {当前 AI 代理}
 date "+%Y-%m-%d %H:%M:%S"
 ```
 
-更新 `.agent-workspace/active/{task-id}/task.md`：
+更新 `.agents/workspace/active/{task-id}/task.md`：
 - `current_step`：requirement-analysis
 - `assigned_to`：{当前 AI 代理}
 - `updated_at`：{当前时间}
@@ -84,7 +84,7 @@ Issue #{number} 已导入。
 - 工作流：{workflow}
 
 产出文件：
-- 任务文件：.agent-workspace/active/{task-id}/task.md
+- 任务文件：.agents/workspace/active/{task-id}/task.md
 
 下一步 - 执行需求分析：
   - Claude Code / OpenCode：/analyze-task {task-id}
@@ -94,7 +94,7 @@ Issue #{number} 已导入。
 
 ## 完成检查清单
 
-- [ ] 创建了任务文件 `.agent-workspace/active/{task-id}/task.md`
+- [ ] 创建了任务文件 `.agents/workspace/active/{task-id}/task.md`
 - [ ] 在 task.md 中记录了 issue_number
 - [ ] 更新了 `current_step` 为 requirement-analysis
 - [ ] 更新了 `updated_at` 为当前时间

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

@@ -20,7 +20,7 @@ description: >
 ### 1. Verify Prerequisites
 
 Check required files:
-- `.agent-workspace/active/{task-id}/task.md` - Task file
+- `.agents/workspace/active/{task-id}/task.md` - Task file
 - At least one analysis artifact: `analysis.md` or `analysis-r{N}.md`
 
 Note: `{task-id}` format is `TASK-{yyyyMMdd-HHmmss}`, for example `TASK-20260306-143022`
@@ -29,7 +29,7 @@ If any required file is missing, prompt the user to complete the prerequisite st
 
 ### 2. Determine the Plan Round
 
-Scan `.agent-workspace/active/{task-id}/` for plan artifact files:
+Scan `.agents/workspace/active/{task-id}/` for plan artifact files:
 - If neither `plan.md` nor `plan-r*.md` exists -> this is Round 1 and must create `plan.md`
 - If `plan.md` exists and no `plan-r*.md` exists -> this is Round 2 and must create `plan-r2.md`
 - If `plan-r{N}.md` exists -> this is Round N+1 and must create `plan-r{N+1}.md`
@@ -77,7 +77,7 @@ Follow the `technical-design` step in `.agents/workflows/feature-development.yam
 
 ### 6. Output Plan Document
 
-Create `.agent-workspace/active/{task-id}/{plan-artifact}`.
+Create `.agents/workspace/active/{task-id}/{plan-artifact}`.
 
 ### 7. Update Task Status
 
@@ -87,7 +87,7 @@ Get the current time:
 date "+%Y-%m-%d %H:%M:%S"
 ```
 
-Update `.agent-workspace/active/{task-id}/task.md`:
+Update `.agents/workspace/active/{task-id}/task.md`:
 - `current_step`: technical-design
 - `assigned_to`: {current AI agent}
 - `updated_at`: {current time}
@@ -115,7 +115,7 @@ Plan summary:
 - Estimated complexity: {assessment}
 
 Output file:
-- Technical plan: .agent-workspace/active/{task-id}/{plan-artifact}
+- Technical plan: .agents/workspace/active/{task-id}/{plan-artifact}
 
 Important: human review checkpoint.
 Please review the technical plan before continuing to implementation.
@@ -200,7 +200,7 @@ Next step - implement the task:
 
 - [ ] Read and understood the requirements analysis
 - [ ] Considered alternative options
-- [ ] Created the plan document `.agent-workspace/active/{task-id}/{plan-artifact}`
+- [ ] Created the plan document `.agents/workspace/active/{task-id}/{plan-artifact}`
 - [ ] Updated `current_step` to technical-design in task.md
 - [ ] Updated `updated_at` to the current time in task.md
 - [ ] Recorded `{plan-artifact}` as a completed artifact in task.md

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

@@ -18,7 +18,7 @@ description: >
 ### 1. 验证前置条件
 
 检查必要文件：
-- `.agent-workspace/active/{task-id}/task.md` - 任务文件
+- `.agents/workspace/active/{task-id}/task.md` - 任务文件
 - 至少一个分析产物：`analysis.md` 或 `analysis-r{N}.md`
 
 注意：`{task-id}` 格式为 `TASK-{yyyyMMdd-HHmmss}`，例如 `TASK-20260306-143022`
@@ -27,7 +27,7 @@ description: >
 
 ### 2. 确定方案轮次
 
-扫描 `.agent-workspace/active/{task-id}/` 目录中的方案产物文件：
+扫描 `.agents/workspace/active/{task-id}/` 目录中的方案产物文件：
 - 如果不存在 `plan.md` 且不存在 `plan-r*.md` → 本轮为第 1 轮，产出 `plan.md`
 - 如果存在 `plan.md` 且不存在 `plan-r*.md` → 本轮为第 2 轮，产出 `plan-r2.md`
 - 如果存在 `plan-r{N}.md` → 本轮为第 N+1 轮，产出 `plan-r{N+1}.md`
@@ -75,7 +75,7 @@ description: >
 
 ### 6. 输出计划文档
 
-创建 `.agent-workspace/active/{task-id}/{plan-artifact}`。
+创建 `.agents/workspace/active/{task-id}/{plan-artifact}`。
 
 ### 7. 更新任务状态
 
@@ -85,7 +85,7 @@ description: >
 date "+%Y-%m-%d %H:%M:%S"
 ```
 
-更新 `.agent-workspace/active/{task-id}/task.md`：
+更新 `.agents/workspace/active/{task-id}/task.md`：
 - `current_step`：technical-design
 - `assigned_to`：{当前 AI 代理}
 - `updated_at`：{当前时间}
@@ -113,7 +113,7 @@ date "+%Y-%m-%d %H:%M:%S"
 - 预估复杂度：{评估}
 
 产出文件：
-- 技术方案：.agent-workspace/active/{task-id}/{plan-artifact}
+- 技术方案：.agents/workspace/active/{task-id}/{plan-artifact}
 
 重要：人工审查检查点。
 请在继续实现之前审查技术方案。
@@ -198,7 +198,7 @@ date "+%Y-%m-%d %H:%M:%S"
 
 - [ ] 阅读并理解了需求分析
 - [ ] 考虑了备选方案
-- [ ] 创建了计划文档 `.agent-workspace/active/{task-id}/{plan-artifact}`
+- [ ] 创建了计划文档 `.agents/workspace/active/{task-id}/{plan-artifact}`
 - [ ] 更新了 task.md 中的 `current_step` 为 technical-design
 - [ ] 更新了 task.md 中的 `updated_at` 为当前时间
 - [ ] 在 task.md 中记录了 `{plan-artifact}` 为已完成产物

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

@@ -20,7 +20,7 @@ description: >
 ### 1. Verify Prerequisites
 
 Check required files:
-- `.agent-workspace/active/{task-id}/task.md` - Task file
+- `.agents/workspace/active/{task-id}/task.md` - Task file
 - At least one review artifact: `review.md` or `review-r{N}.md`
 
 Note: `{task-id}` format is `TASK-{yyyyMMdd-HHmmss}`, for example `TASK-20260306-143022`
@@ -86,7 +86,7 @@ Ensure all tests still pass after the fixes.
 
 ### 6. Create Refinement Report
 
-Create `.agent-workspace/active/{task-id}/{refinement-artifact}`.
+Create `.agents/workspace/active/{task-id}/{refinement-artifact}`.
 
 ### 7. Update Task Status
 
@@ -96,7 +96,7 @@ Get the current time:
 date "+%Y-%m-%d %H:%M:%S"
 ```
 
-Update `.agent-workspace/active/{task-id}/task.md`:
+Update `.agents/workspace/active/{task-id}/task.md`:
 - `current_step`: refinement
 - `assigned_to`: {current AI agent}
 - `updated_at`: {current time}

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

@@ -18,7 +18,7 @@ description: >
 ### 1. 验证前置条件
 
 检查必要文件：
-- `.agent-workspace/active/{task-id}/task.md` - 任务文件
+- `.agents/workspace/active/{task-id}/task.md` - 任务文件
 - 至少一个审查产物：`review.md` 或 `review-r{N}.md`
 
 注意：`{task-id}` 格式为 `TASK-{yyyyMMdd-HHmmss}`，例如 `TASK-20260306-143022`
@@ -84,7 +84,7 @@ description: >
 
 ### 6. 创建修复报告
 
-创建 `.agent-workspace/active/{task-id}/{refinement-artifact}`。
+创建 `.agents/workspace/active/{task-id}/{refinement-artifact}`。
 
 ### 7. 更新任务状态
 
@@ -94,7 +94,7 @@ description: >
 date "+%Y-%m-%d %H:%M:%S"
 ```
 
-更新 `.agent-workspace/active/{task-id}/task.md`：
+更新 `.agents/workspace/active/{task-id}/task.md`：
 - `current_step`：refinement
 - `assigned_to`：{当前 AI 代理}
 - `updated_at`：{当前时间}

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

@@ -31,7 +31,26 @@ git status --short
 
 If there are uncommitted changes, error: "Workspace has uncommitted changes. Please commit or stash first."
 
-### Step 3: Update Version References
+### Step 3: Pre-release Verification
+
+<!-- TODO: Replace with your project's pre-release verification steps -->
+
+Run any checks that must pass before preparing a release:
+
+```bash
+git branch --show-current
+# TODO: Replace with your project's test/build verification commands
+```
+
+Verification guidance:
+- Confirm the release is being prepared from the correct branch for your project
+- Run the full validation commands required by your release process
+
+Handling rules:
+- If the current branch is unexpected, print a warning or exit based on your policy
+- If any verification command fails, stop the release process and fix the issue first
+
+### Step 4: Update Version References
 
 <!-- TODO: Replace with your project's version update steps -->
 
@@ -45,6 +64,7 @@ Search for version references in project files and update them:
 
 **Common files to update**:
 - `package.json` (Node.js)
+- `package-lock.json` (Node.js; run `npm install --package-lock-only` after updating `package.json`)
 - `pom.xml` (Maven)
 - `setup.py` / `pyproject.toml` (Python)
 - `version.go` (Go)
@@ -52,22 +72,39 @@ Search for version references in project files and update them:
 - `SECURITY.md` / `SECURITY.zh-CN.md` (supported version table)
 
 **Exclude from version replacement**:
-- `.agents/`, `.agent-workspace/`, `.claude/`, `.codex/`, `.gemini/`, `.opencode/` (AI tool configs)
+- `.agents/`, `.agents/workspace/`, `.claude/`, `.codex/`, `.gemini/`, `.opencode/` (AI tool configs)
+
+If the project uses `package-lock.json`, run `npm install --package-lock-only` after updating `package.json` so the lockfile version stays in sync.
+
+### Step 5: Rebuild Artifacts
 
-### Step 4: Create Release Commit
+<!-- TODO: Replace with your project's artifact rebuild steps -->
+
+If version updates affect generated files, embedded metadata, or bundled assets, rebuild them now:
+
+```bash
+# TODO: Replace with your project's rebuild command(s)
+```
+
+Execution guidance:
+- Run this after updating version references so generated artifacts pick up the new version
+- If your project has no generated artifacts, document that explicitly in the project-specific skill
+- If the rebuild fails, stop the release process and fix the build first
+
+### Step 6: Create Release Commit
 
 ```bash
 git add -A
 git commit -m "chore: release v{version}"
 ```
 
-### Step 5: Create Git Tag
+### Step 7: Create Git Tag
 
 ```bash
 git tag v{version}
 ```
 
-### Step 6: Manage Milestones
+### Step 8: Manage Milestones
 
 Close the milestone for the released version when it exists, and create the missing planning milestones for the next cycle.
 
@@ -84,7 +121,7 @@ The script is responsible for:
 - When `PATCH=0`, also ensuring `{MAJOR}.{MINOR+1}.0` and `{MAJOR}.{MINOR+1}.x`
 - Printing a milestone summary with the released milestone action and new milestone count
 
-### Step 7: Output Summary
+### Step 9: Output Summary
 
 > **IMPORTANT**: All TUI command formats listed below must be output in full. Do not show only the format for the current AI agent.
 
@@ -100,12 +137,12 @@ Files updated: {count}
 
 Next steps (manual):
 
-1. Push tag:
-   git push origin v{version}
-
-2. Push branch:
+1. Push branch:
    git push origin {current-branch}
 
+2. Push tag:
+   git push origin v{version}
+
 3. (Optional) Generate release notes:
    - Claude Code / OpenCode: /create-release-note {version}
    - Gemini CLI: /{{project}}:create-release-note {version}
@@ -130,13 +167,17 @@ git checkout -- .
 
 1. **Clean workspace required**: Must have no uncommitted changes
 2. **No auto-push**: All operations are local only; user pushes manually
-3. **No build verification**: Run the test skill before releasing to verify
-4. **Version replacement scope**: Search determines which files to update; exclude AI tool directories
-5. **Adapt to your project**: The version update steps above are generic; customize for your project's versioning scheme
-6. **Milestone coordination**: Releases should create the next planning milestones automatically; initialize the taxonomy first with `init-milestones` when needed
+3. **Pre-release verification**: Replace the Step 3 TODOs with the branch, test, and validation commands your release process requires
+4. **Generated artifacts**: Replace the Step 5 TODOs when version changes affect generated files, bundled assets, or embedded metadata
+5. **Release automation**: If pushing a tag triggers CI/CD or package publishing, confirm the required credentials and pipeline settings first
+6. **Version replacement scope**: Search determines which files to update; exclude AI tool directories
+7. **Adapt to your project**: The version update and rebuild steps above are generic; customize them for your project's versioning scheme
+8. **Milestone coordination**: Releases should create the next planning milestones automatically; initialize the taxonomy first with `init-milestones` when needed
 
 ## Error Handling
 
 - Invalid version format: Prompt correct format and exit
 - Dirty workspace: Prompt to commit or stash
+- Verification failure: Display the failing check and stop the release
+- Artifact rebuild failure: Display the build error and stop the release
 - Git operation failure: Display error and provide rollback instructions