@fitlab-ai/agent-infra 0.3.2 → 0.4.1

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

@@ -1,8 +1,6 @@
 ---
 name: import-issue
-description: >
-  从 GitHub Issue 导入并创建任务文件。
-  当用户要求导入某个 Issue 时触发。参数：issue 编号。
+description: "从 GitHub Issue 导入并创建任务"
 ---
 
 # 导入 Issue
@@ -27,7 +25,7 @@ gh issue view <issue-number> --json number,title,body,labels
 
 ### 2. 检查已有任务
 
-搜索 `.agent-workspace/active/` 中是否已有链接到此 Issue 的任务。
+搜索 `.agents/workspace/active/` 中是否已有链接到此 Issue 的任务。
 - 如果找到，询问用户是重新导入还是继续使用现有任务
 - 如果未找到，创建新任务
 
@@ -37,7 +35,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 +60,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 +82,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 +92,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/init-labels/SKILL.md

@@ -1,9 +1,6 @@
 ---
 name: init-labels
-description: >
-  Initialize the repository's standard GitHub Labels taxonomy in one pass.
-  Create the common labels, auto-detect `in:` labels from the project structure,
-  do not create `theme:` labels, overwrite exact-match GitHub defaults, and report unmatched defaults.
+description: "Initialize the repository's standard GitHub Labels taxonomy"
 ---
 
 # Initialize GitHub Labels

package/templates/.agents/skills/init-labels/SKILL.zh-CN.md

@@ -1,9 +1,6 @@
 ---
 name: init-labels
-description: >
-  一次性初始化仓库的标准 GitHub Labels 体系。
-  创建通用 labels、基于项目目录结构自动探测 `in:` labels、
-  不创建 `theme:` labels、覆盖名称完全匹配的 GitHub 默认 labels，并提示未覆盖的默认 labels。
+description: "初始化仓库的 GitHub Labels 体系"
 ---
 
 # 初始化 GitHub Labels

package/templates/.agents/skills/init-milestones/SKILL.md

@@ -1,8 +1,6 @@
 ---
 name: init-milestones
-description: >
-  Initialize the repository's standard GitHub Milestones taxonomy in one pass.
-  Create General Backlog, the initial milestones derived from the current version baseline, and optionally backfill historical milestones.
+description: "Initialize the repository's standard GitHub Milestones taxonomy"
 ---
 
 # Initialize GitHub Milestones

package/templates/.agents/skills/init-milestones/SKILL.zh-CN.md

@@ -1,8 +1,6 @@
 ---
 name: init-milestones
-description: >
-  一次性初始化仓库的标准 GitHub Milestones 体系。
-  创建 General Backlog、基于当前版本的初始里程碑，并可选补齐历史版本里程碑。
+description: "初始化仓库的 GitHub Milestones 体系"
 ---
 
 # 初始化 GitHub Milestones

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

@@ -1,10 +1,6 @@
 ---
 name: plan-task
-description: >
-  Design a technical plan for a task and output a detailed implementation
-  plan. Triggered when the user asks for a design or technical plan after
-  requirements analysis is complete. This is a mandatory human review
-  checkpoint. Argument: task-id.
+description: "Design a technical plan for a task"
 ---
 
 # Design Technical Plan
@@ -20,7 +16,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 +25,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 +73,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 +83,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 +111,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 +196,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

@@ -1,8 +1,6 @@
 ---
 name: plan-task
-description: >
-  为任务设计技术方案并输出详细的实施计划。当用户要求为已完成需求分析的任务设计方案或技术计划时触发。
-  这是一个强制性的人工审查检查点。参数：task-id。
+description: "为任务设计技术方案和实施计划"
 ---
 
 # 设计技术方案
@@ -18,7 +16,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 +25,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 +73,7 @@ description: >
 
 ### 6. 输出计划文档
 
-创建 `.agent-workspace/active/{task-id}/{plan-artifact}`。
+创建 `.agents/workspace/active/{task-id}/{plan-artifact}`。
 
 ### 7. 更新任务状态
 
@@ -85,7 +83,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 +111,7 @@ date "+%Y-%m-%d %H:%M:%S"
 - 预估复杂度：{评估}
 
 产出文件：
-- 技术方案：.agent-workspace/active/{task-id}/{plan-artifact}
+- 技术方案：.agents/workspace/active/{task-id}/{plan-artifact}
 
 重要：人工审查检查点。
 请在继续实现之前审查技术方案。
@@ -198,7 +196,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

@@ -1,94 +1,52 @@
 ---
 name: refine-task
-description: >
-  Process code review feedback and fix the issues found in review. Fix items by
-  priority (Blocker -> Major -> Minor). Only handle issues explicitly marked in
-  the review; do not add unrelated changes. Triggered when the user asks to fix
-  review findings. Argument: task-id.
+description: "Handle code review feedback and fix issues"
 ---
 
-# Refine Review Findings
+# Refine Task
+
+Fix review findings and produce `refinement.md` or `refinement-r{N}.md`.
 
 ## Boundary / Critical Rules
 
-- Only fix issues that were explicitly identified in review -- do not add unrelated changes or extra "improvements"
-- Do NOT auto-commit. Never execute `git commit` or `git add`
-- After executing this skill, you **must** immediately update task status in task.md
+- Fix only the issues documented in review artifacts
+- Never auto-run `git add` or `git commit`
+- After executing this skill, you **must** immediately update task.md
 
 ## Steps
 
 ### 1. Verify Prerequisites
 
-Check required files:
-- `.agent-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`
-
-If `task.md` is missing or there is no review artifact, prompt the user to complete the prerequisite step first.
+Require:
+- `.agents/workspace/active/{task-id}/task.md`
+- at least one review artifact: `review.md` or `review-r{N}.md`
 
-Then perform this discovery and validation:
-1. Scan review artifact files in the task directory (`review.md`, `review-r{N}.md`)
-2. Use the highest-round review artifact as the input for this refinement round and record it as `{review-artifact}`
-3. Scan refinement artifact files (`refinement.md`, `refinement-r{N}.md`) and determine the current refinement artifact:
-   - If neither `refinement.md` nor `refinement-r*.md` exists -> this is Round 1 and must create `refinement.md`
-   - If `refinement.md` exists and no `refinement-r*.md` exists -> this is Round 2 and must create `refinement-r2.md`
-   - If `refinement-r{N}.md` exists -> this is Round N+1 and must create `refinement-r{N+1}.md`
-   - Record `{refinement-round}` and `{refinement-artifact}`
-4. Scan implementation report files (`implementation.md`, `implementation-r{N}.md`) and use the highest-round artifact as the implementation context `{implementation-artifact}`
-   - Record `{implementation-artifact}`
-5. **Consistency check**: verify that the most recent Code Review entry in `task.md` `## Activity Log` matches the round number and filename of the latest review artifact found in Step 2
+During prerequisite discovery, record `{review-artifact}`, `{refinement-round}`, `{refinement-artifact}`, and Record `{implementation-artifact}` from the latest implementation report.
 
-If the Activity Log entry does not match the actual file, stop immediately and prompt:
+Also validate the latest Code Review entry in Activity Log. If it points to a missing file, stop with:
 `Review artifact mismatch: Activity Log references {expected} but file not found. Please verify the review artifact exists.`
 
 ### 2. Read Review and Implementation Context
 
-Carefully read the latest review artifact `{review-artifact}` and implementation artifact `{implementation-artifact}` identified in Step 1 to understand:
-- All blockers (must fix)
-- All major issues (should fix)
-- Minor issues (optional improvements)
-- Reviewer recommendations and suggestions
-- The context of the current implementation and previous refinements
-
-### 3. Plan the Fixes
-
-Classify and prioritize:
-1. **Blockers first**: all blockers must be resolved
-2. **Then major issues**: handle all major issues
-3. **Finally minor issues**: fix if appropriate (optional)
+Read the latest `{review-artifact}` and `{implementation-artifact}` before editing any code.
 
-For each issue, determine:
-- Which files need to be modified
-- What exact change is required
-- How to verify the fix
+### 3. Plan and Apply the Fixes
 
-### 4. Execute the Fixes
+Prioritize Blocker -> Major -> Minor and keep changes tightly scoped.
 
-Fix issues in priority order:
+> The detailed fix workflow, repair order, and verification loop live in `reference/fix-workflow.md`. Read `reference/fix-workflow.md` before making changes.
 
-**For each fix**:
-1. Read the affected file
-2. Apply the fix
-3. Verify that the change resolves the review finding
-4. Run relevant tests
+### 4. Run Test Verification
 
-**Refinement principles**:
-- Only fix marked review issues -- do not add unrelated changes
-- Do not add extra "improvements" beyond the scope of the review
-- Keep the changes minimal and focused
+Run the project test command after the fixes and keep the repair cycle focused on the documented findings.
 
-### 5. Run Test Verification
+### 5. Write the Refinement Report
 
-Execute the project's test command. Reference the `test` skill for the project-specific test command.
+Create `.agents/workspace/active/{task-id}/{refinement-artifact}`.
 
-Ensure all tests still pass after the fixes.
+> The report structure and example sections live in `reference/report-template.md`. Read `reference/report-template.md` before writing the report.
 
-### 6. Create Refinement Report
-
-Create `.agent-workspace/active/{task-id}/{refinement-artifact}`.
-
-### 7. Update Task Status
+### 6. Update Task Status
 
 Get the current time:
 
@@ -96,115 +54,33 @@ Get the current time:
 date "+%Y-%m-%d %H:%M:%S"
 ```
 
-Update `.agent-workspace/active/{task-id}/task.md`:
-- `current_step`: refinement
-- `assigned_to`: {current AI agent}
-- `updated_at`: {current time}
-- Record the refinement artifact for this round: `{refinement-artifact}` (Round `{refinement-round}`)
-- **Append** to `## Activity Log` (do NOT overwrite previous entries):
-  ```
-  - {yyyy-MM-dd HH:mm:ss} — **Refinement (Round {N}, for {review-artifact})** by {agent} — Fixed {n} blockers, {n} major, {n} minor issues → {refinement-artifact}
-  ```
-
-### 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.
-
-> **⚠️ CONDITION CHECK — before showing the two next steps below, you must judge the result of this refinement round first:**
->
-> - If this round fixed any `Blocker` or `Major` issue, or the changes touched core logic or test scope broadly, **default recommendation** is "Run review again"
-> - If this round fixed only `Minor` issues and the change scope is small and low-risk, "Commit directly" may be offered as an option
-> - If any `Blocker` or `Major` issue remains unresolved, **do not** imply that direct commit is acceptable; explicitly tell the user to continue fixing or re-run review
->
-> **Do not present "Commit directly" as the default path unless you are sure no high-risk issue remains.**
-
-Output format:
-```
-Refinement complete for task {task-id}.
-
-Fix summary:
-- Blockers fixed: {count}/{total}
-- Major issues fixed: {count}/{total}
-- Minor issues fixed: {count}/{total}
-- All tests passing: {yes/no}
-- Review input: {review-artifact}
-- Refinement artifact: {refinement-artifact}
-
-Next step - re-review or commit:
-- Run review again (default recommendation; prioritize this after Blocker/Major fixes):
-  - Claude Code / OpenCode: /review-task {task-id}
-  - Gemini CLI: /{{project}}:review-task {task-id}
-  - Codex CLI: $review-task {task-id}
-- Commit directly (only when only Minor issues were fixed and risk is low):
-  - Claude Code / OpenCode: /commit
-  - Gemini CLI: /{{project}}:commit
-  - Codex CLI: $commit
-```
+Update task.md and append:
+`- {yyyy-MM-dd HH:mm:ss} — **Refinement (Round {N}, for {review-artifact})** by {agent} — Fixed {n} blockers, {n} major, {n} minor issues → {refinement-artifact}`
 
-## Output Template
+### 7. Inform User
 
-```markdown
-# Refinement Report
-
-- **Refinement round**: Round {refinement-round}
-- **Artifact file**: `{refinement-artifact}`
-- **Review input**: `{review-artifact}`
-- **Implementation context**: `{implementation-artifact}`
-
-### Review Feedback Handling
-
-#### Blocker Fixes
-1. **{Issue title}** (from {review-artifact})
-   - **Fix**: {What changed}
-   - **File**: `{file-path}:{line-number}`
-   - **Validation**: {How it was verified}
-
-#### Major Issue Fixes
-1. **{Issue title}** (from {review-artifact})
-   - **Fix**: {What changed}
-   - **File**: `{file-path}:{line-number}`
-
-#### Minor Issue Handling
-1. **{Issue title}** (from {review-artifact})
-   - **Fix**: {What changed}
-
-#### Unresolved Issues
-- {Issue}: {Reason it was not handled, for example disagreement with the review suggestion}
-
-### Test Results After Refinement
-- All tests passing: {yes/no}
-- Test output: {Summary}
-```
+Recommend re-review by default when Blocker or Major issues were fixed. Only present direct commit as a low-risk option when the changes are truly minor.
 
 ## Completion Checklist
 
-- [ ] Read and understood all review findings
-- [ ] Fixed all blockers
-- [ ] Fixed all major issues
-- [ ] Addressed minor issues when appropriate
-- [ ] All tests pass after the fixes
-- [ ] Created refinement report `{refinement-artifact}`
-- [ ] Updated task status in task.md
-- [ ] Appended an Activity Log entry to task.md
-- [ ] Informed the user of the next step (must include all TUI command formats without filtering)
+- [ ] Read the latest review and implementation context
+- [ ] Fixed all required Blocker and Major findings
+- [ ] Wrote `{refinement-artifact}`
+- [ ] Updated task.md and appended the Activity Log entry
+- [ ] Recommended the correct next step based on residual risk
 
 ## Notes
 
-1. **Prerequisite**: A review report must exist (`review.md` or `review-r{N}.md`)
-2. **No auto-commit**: Do NOT execute `git commit`. Remind the user to commit manually
-3. **Scope discipline**: Only fix issues marked in review -- do not add extra changes
-4. **Disagreement**: If you disagree with a review finding, record your reasoning in "Unresolved Issues"
-5. **Re-review**: After fixing blockers, re-run `review-task` to validate the result
-6. **Consistency requirement**: The latest review artifact, Activity Log entry, and refinement report title must all reference the same review round
-7. **Versioning rule**: First refinement uses `refinement.md`; later rounds use `refinement-r{N}.md`
+- Round 1 uses `refinement.md`; later rounds use `refinement-r{N}.md`
+- Record any disagreement with a review comment under unresolved issues in the report
+- Do not expand scope beyond the review findings
 
 ## STOP
 
-After completing the checklist, **stop immediately**. Wait for the user to review the fixes and decide whether to run review again or commit.
+Stop after the checklist is complete.
 
 ## Error Handling
 
-- Task not found: Prompt "Task {task-id} not found"
-- Missing review report: Prompt "Review report not found, please run the review-task skill first"
-- Review artifact mismatch: Prompt "Review artifact mismatch: Activity Log references {expected} but file not found. Please verify the review artifact exists."
-- Test failure after fixes: Output the test errors and ask the user how to proceed
+- Task not found: `Task {task-id} not found`
+- Missing review report: `Review report not found, please run the review-task skill first`
+- Review artifact mismatch: `Review artifact mismatch: Activity Log references {expected} but file not found. Please verify the review artifact exists.`