@fitlab-ai/agent-infra 0.3.2 → 0.4.1

package/templates/.agents/workflows/feature-development.yaml

@@ -1,150 +1,150 @@
-# 功能开发工作流
-# 实现新功能时使用此工作流。
+# Feature Development Workflow
+# Use this workflow when implementing a new feature.
 
 name: feature-development
-description: 开发新功能的端到端工作流。
+description: End-to-end workflow for developing a new feature.
 
 steps:
   - name: analysis
-    description: 分析功能需求，探索代码库，识别受影响的区域。
+    description: Analyze feature requirements, explore the codebase, and identify impacted areas.
     recommended_agents:
       - claude
       - gemini
     tasks:
-      - 阅读并理解功能需求
-      - 探索代码库以识别相关文件和模块
-      - 识别依赖项和潜在影响区域
-      - 将发现记录在任务文件中
+      - Read and understand the feature requirements
+      - Explore the codebase to identify relevant files and modules
+      - Identify dependencies and potentially impacted areas
+      - Record findings in the task file
     inputs:
-      - 功能需求或 Issue 描述
-      - 项目代码库
+      - Feature requirements or issue description
+      - Project codebase
     artifact_versioning:
       outputs:
         - name: analysis
           pattern: "analysis.md | analysis-r{N}.md"
-          rule: "扫描现有分析产物；首轮创建 analysis.md，后续修订创建 analysis-r{N}.md（N = 当前最高轮次 + 1）"
+          rule: "Scan existing analysis artifacts; create analysis.md for the first round, then analysis-r{N}.md for later revisions (N = current highest round + 1)"
     outputs:
-      - 更新后的任务文件（分析部分）
-      - 受影响文件列表
-      - 识别的风险或约束
+      - Updated task file (analysis section)
+      - List of impacted files
+      - Identified risks or constraints
 
   - name: design
-    description: 为功能实现创建技术设计方案。
+    description: Create the technical design for the feature implementation.
     recommended_agents:
       - claude
       - gemini
     tasks:
-      - 定义接口和数据结构
-      - 概述实现方案
-      - 识别边界情况和错误处理策略
-      - 在任务文件中记录设计方案
+      - Define interfaces and data structures
+      - Outline the implementation approach
+      - Identify edge cases and error-handling strategies
+      - Record the design in the task file
     inputs:
-      - 上一步的分析结果
-      - 项目架构和规范
+      - Analysis results from the previous step
+      - Project architecture and conventions
     artifact_versioning:
       inputs:
         - name: analysis
           pattern: "analysis.md | analysis-r{N}.md"
-          rule: "读取最高轮次的分析产物作为设计输入"
+          rule: "Read the highest-round analysis artifact as design input"
       outputs:
         - name: plan
           pattern: "plan.md | plan-r{N}.md"
-          rule: "扫描现有方案产物；首轮创建 plan.md，后续修订创建 plan-r{N}.md（N = 当前最高轮次 + 1）"
+          rule: "Scan existing plan artifacts; create plan.md for the first round, then plan-r{N}.md for later revisions (N = current highest round + 1)"
     outputs:
-      - 更新后的任务文件（设计部分）
-      - 接口定义
-      - 实现计划
+      - Updated task file (design section)
+      - Interface definitions
+      - Implementation plan
 
   - name: implementation
-    description: 按照设计方案实现功能。
+    description: Implement the feature according to the design plan.
     recommended_agents:
       - codex
       - cursor
     tasks:
-      - 创建功能分支
-      - 实现功能代码
-      - 编写单元测试
-      - 编写集成测试（如适用）
-      - 确保代码遵循项目规范
+      - Create a feature branch
+      - Implement the feature code
+      - Write unit tests
+      - Write integration tests when applicable
+      - Ensure the code follows project conventions
     inputs:
-      - 上一步的技术设计
-      - 项目编码标准
+      - Technical design from the previous step
+      - Project coding standards
     artifact_versioning:
       outputs:
         - name: implementation
           pattern: "implementation.md | implementation-r{N}.md"
-          rule: "扫描现有实现产物；首轮创建 implementation.md，后续重实现创建 implementation-r{N}.md（N = 当前最高轮次 + 1）"
+          rule: "Scan existing implementation artifacts; create implementation.md for the first round, then implementation-r{N}.md for later re-implementations (N = current highest round + 1)"
     outputs:
-      - 包含实现的功能分支
-      - 测试文件
-      - 更新后的任务文件（实现备注）
+      - Feature branch with the implementation
+      - Test files
+      - Updated task file (implementation notes)
 
   - name: review
-    description: 审查实现的正确性、代码风格和最佳实践。
+    description: Review correctness, code style, and best practices in the implementation.
     recommended_agents:
       - claude
     tasks:
-      - 审查代码变更的正确性
-      - 检查是否遵循项目规范
-      - 验证测试覆盖率和质量
-      - 检查安全和性能问题
-      - 创建审查报告
+      - Review the correctness of the code changes
+      - Check adherence to project conventions
+      - Verify test coverage and quality
+      - Check for security and performance issues
+      - Create a review report
     inputs:
-      - 实现分支
-      - 项目规范
+      - Implementation branch
+      - Project conventions
     artifact_versioning:
       inputs:
         - name: implementation
           pattern: "implementation.md | implementation-r{N}.md"
-          rule: "读取最高轮次的实现产物作为审查输入"
+          rule: "Read the highest-round implementation artifact as review input"
       outputs:
         - name: review
           pattern: "review.md | review-r{N}.md"
-          rule: "扫描现有审查产物；首轮创建 review.md，后续轮次创建 review-r{N}.md（N = 当前最高轮次 + 1）"
+          rule: "Scan existing review artifacts; create review.md for the first round, then review-r{N}.md for later rounds (N = current highest round + 1)"
     outputs:
-      - 审查报告
-      - 待修复问题列表
+      - Review report
+      - List of issues to fix
 
   - name: fix
-    description: 处理审查阶段发现的问题。
+    description: Address issues found during the review step.
     recommended_agents:
       - codex
       - cursor
     tasks:
-      - 修复审查中的所有严重和重要问题
-      - 酌情处理次要问题和建议
-      - 根据需要更新测试
-      - 验证所有测试通过
+      - Fix all critical and major review findings
+      - Address minor issues and suggestions when appropriate
+      - Update tests as needed
+      - Verify that all tests pass
     inputs:
-      - 审查报告
-      - 实现分支
+      - Review report
+      - Implementation branch
     artifact_versioning:
       inputs:
         - name: review
           pattern: "review.md | review-r{N}.md"
-          rule: "读取最高轮次的审查产物，并校验其与 task.md Activity Log 中最近一条 Code Review 记录一致"
+          rule: "Read the highest-round review artifact and verify that it matches the latest Code Review entry in the task.md Activity Log"
       outputs:
         - name: refinement
           pattern: "refinement.md | refinement-r{N}.md"
-          rule: "扫描现有修复产物；首轮创建 refinement.md，后续轮次创建 refinement-r{N}.md（N = 当前最高轮次 + 1）"
+          rule: "Scan existing refinement artifacts; create refinement.md for the first round, then refinement-r{N}.md for later rounds (N = current highest round + 1)"
     outputs:
-      - 包含修复的更新分支
-      - 更新后的任务文件
+      - Updated branch with fixes
+      - Updated task file
 
   - name: commit
-    description: 最终确认变更并创建拉取请求。
+    description: Finalize the changes and create a pull request.
     recommended_agents:
       - claude
       - human
     tasks:
-      - 确保所有测试通过
-      - 按规范编写清晰的提交信息
-      - 创建包含适当描述的拉取请求
-      - 将 PR 关联到相关 Issue
-      - 将任务移至已完成
+      - Ensure all tests pass
+      - Write a clear commit message that follows project conventions
+      - Create a pull request with an appropriate description
+      - Link the PR to the relevant issue
+      - Move the task to completed
     inputs:
-      - 最终实现分支
-      - 任务文件
+      - Final implementation branch
+      - Task file
     outputs:
-      - 拉取请求
-      - 已完成的任务文件（位于 .agent-workspace/completed/）
+      - Pull request
+      - Completed task file (stored in .agents/workspace/completed/)

package/templates/.agents/workflows/feature-development.zh-CN.yaml

@@ -147,4 +147,4 @@ steps:
       - 任务文件
     outputs:
       - 拉取请求
-      - 已完成的任务文件（位于 .agent-workspace/completed/）
+      - 已完成的任务文件（位于 .agents/workspace/completed/）

package/templates/.agents/workflows/refactoring.yaml

@@ -1,154 +1,154 @@
-# 重构工作流
-# 代码重构任务时使用此工作流。
+# Refactoring Workflow
+# Use this workflow for code refactoring tasks.
 
 name: refactoring
-description: 安全且结构化的代码重构工作流。
+description: Safe and structured workflow for code refactoring.
 
 steps:
   - name: analysis
-    description: 分析当前代码并确定重构范围。
+    description: Analyze the current code and determine the refactoring scope.
     recommended_agents:
       - claude
       - gemini
     tasks:
-      - 识别待重构的代码及重构原因
-      - 映射受影响代码的所有依赖项和使用者
-      - 评估重构的风险和复杂度
-      - 识别受影响区域的现有测试覆盖
-      - 将发现记录在任务文件中
+      - Identify the code to refactor and why it needs refactoring
+      - Map all dependencies and consumers of the impacted code
+      - Assess refactoring risk and complexity
+      - Identify existing test coverage for impacted areas
+      - Record findings in the task file
     inputs:
-      - 重构请求或 Issue 描述
-      - 项目代码库
+      - Refactoring request or issue description
+      - Project codebase
     artifact_versioning:
       outputs:
         - name: analysis
           pattern: "analysis.md | analysis-r{N}.md"
-          rule: "扫描现有分析产物；首轮创建 analysis.md，后续修订创建 analysis-r{N}.md（N = 当前最高轮次 + 1）"
+          rule: "Scan existing analysis artifacts; create analysis.md for the first round, then analysis-r{N}.md for later revisions (N = current highest round + 1)"
     outputs:
-      - 包含依赖关系图的范围分析
-      - 风险评估
-      - 更新后的任务文件（分析部分）
+      - Scope analysis with dependency mapping
+      - Risk assessment
+      - Updated task file (analysis section)
 
   - name: design
-    description: 规划重构方案以最小化风险。
+    description: Plan the refactoring approach to minimize risk.
     recommended_agents:
       - claude
     tasks:
-      - 定义目标架构或代码结构
-      - 规划增量重构步骤（避免一次性大改动）
-      - 识别应保持功能正常的中间状态
-      - 规划重构前需要的额外测试
-      - 在任务文件中记录重构计划
+      - Define the target architecture or code structure
+      - Plan incremental refactoring steps to avoid a single large change
+      - Identify intermediate states that must remain functional
+      - Plan any additional tests needed before refactoring
+      - Record the refactoring plan in the task file
     inputs:
-      - 上一步的范围分析
-      - 项目架构
+      - Scope analysis from the previous step
+      - Project architecture
     artifact_versioning:
       inputs:
         - name: analysis
           pattern: "analysis.md | analysis-r{N}.md"
-          rule: "读取最高轮次的分析产物作为设计输入"
+          rule: "Read the highest-round analysis artifact as design input"
       outputs:
         - name: plan
           pattern: "plan.md | plan-r{N}.md"
-          rule: "扫描现有方案产物；首轮创建 plan.md，后续修订创建 plan-r{N}.md（N = 当前最高轮次 + 1）"
+          rule: "Scan existing plan artifacts; create plan.md for the first round, then plan-r{N}.md for later revisions (N = current highest round + 1)"
     outputs:
-      - 包含增量步骤的重构计划
-      - 前置测试列表
-      - 更新后的任务文件（设计部分）
+      - Refactoring plan with incremental steps
+      - List of prerequisite tests
+      - Updated task file (design section)
 
   - name: implementation
-    description: 按计划执行重构。
+    description: Execute the refactoring according to the plan.
     recommended_agents:
       - codex
       - cursor
     tasks:
-      - 创建重构分支
-      - 添加前置测试（如尚未存在）
-      - 增量执行重构步骤
-      - 每步后验证测试通过
-      - 更新受影响的文档或注释
-      - 确保代码遵循项目规范
+      - Create a refactoring branch
+      - Add prerequisite tests if they do not already exist
+      - Execute the refactoring incrementally
+      - Verify tests pass after each step
+      - Update impacted documentation or comments
+      - Ensure the code follows project conventions
     inputs:
-      - 上一步的重构计划
-      - 项目编码标准
+      - Refactoring plan from the previous step
+      - Project coding standards
     artifact_versioning:
       outputs:
         - name: implementation
           pattern: "implementation.md | implementation-r{N}.md"
-          rule: "扫描现有实现产物；首轮创建 implementation.md，后续重实现创建 implementation-r{N}.md（N = 当前最高轮次 + 1）"
+          rule: "Scan existing implementation artifacts; create implementation.md for the first round, then implementation-r{N}.md for later re-implementations (N = current highest round + 1)"
     outputs:
-      - 包含变更的重构分支
-      - 更新或新增的测试文件
-      - 更新后的任务文件（实现备注）
+      - Refactoring branch with the changes
+      - Updated or new test files
+      - Updated task file (implementation notes)
 
   - name: review
-    description: 验证重构是否保持了行为并提升了代码质量。
+    description: Verify that the refactoring preserves behavior and improves code quality.
     recommended_agents:
       - claude
     tasks:
-      - 验证功能等价性（除非有意改变，否则行为不变）
-      - 检查所有测试通过
-      - 验证代码质量提升
-      - 检查是否有遗漏的依赖项或使用者
-      - 评估性能影响（如适用）
-      - 创建审查报告
+      - Verify functional equivalence unless behavior changes are intentional
+      - Check that all tests pass
+      - Confirm that code quality has improved
+      - Check for missed dependencies or consumers
+      - Assess performance impact when applicable
+      - Create a review report
     inputs:
-      - 重构分支
-      - 原始代码用于对比
-      - 测试结果
+      - Refactoring branch
+      - Original code for comparison
+      - Test results
     artifact_versioning:
       inputs:
         - name: implementation
           pattern: "implementation.md | implementation-r{N}.md"
-          rule: "读取最高轮次的实现产物作为审查输入"
+          rule: "Read the highest-round implementation artifact as review input"
       outputs:
         - name: review
           pattern: "review.md | review-r{N}.md"
-          rule: "扫描现有审查产物；首轮创建 review.md，后续轮次创建 review-r{N}.md（N = 当前最高轮次 + 1）"
+          rule: "Scan existing review artifacts; create review.md for the first round, then review-r{N}.md for later rounds (N = current highest round + 1)"
     outputs:
-      - 审查报告
-      - 问题列表（如有）
+      - Review report
+      - List of issues if any
 
   - name: fix
-    description: 处理审查中发现的问题。
+    description: Address issues found during review.
     recommended_agents:
       - codex
       - cursor
     tasks:
-      - 修复审查中识别的问题
-      - 根据需要更新测试
-      - 验证所有测试通过
-      - 确保无回归问题
+      - Fix issues identified in the review
+      - Update tests as needed
+      - Verify that all tests pass
+      - Ensure there are no regressions
     inputs:
-      - 审查报告
-      - 重构分支
+      - Review report
+      - Refactoring branch
     artifact_versioning:
       inputs:
         - name: review
           pattern: "review.md | review-r{N}.md"
-          rule: "读取最高轮次的审查产物，并校验其与 task.md Activity Log 中最近一条 Code Review 记录一致"
+          rule: "Read the highest-round review artifact and verify that it matches the latest Code Review entry in the task.md Activity Log"
       outputs:
         - name: refinement
           pattern: "refinement.md | refinement-r{N}.md"
-          rule: "扫描现有修复产物；首轮创建 refinement.md，后续轮次创建 refinement-r{N}.md（N = 当前最高轮次 + 1）"
+          rule: "Scan existing refinement artifacts; create refinement.md for the first round, then refinement-r{N}.md for later rounds (N = current highest round + 1)"
     outputs:
-      - 包含修复的更新分支
-      - 更新后的任务文件
+      - Updated branch with fixes
+      - Updated task file
 
   - name: commit
-    description: 最终确认重构并创建拉取请求。
+    description: Finalize the refactoring and create a pull request.
     recommended_agents:
       - claude
       - human
     tasks:
-      - 确保所有测试通过
-      - 编写清晰的提交信息说明重构内容
-      - 创建包含详细变更描述的拉取请求
-      - 将 PR 关联到相关 Issue
-      - 将任务移至已完成
+      - Ensure all tests pass
+      - Write a clear commit message that explains the refactoring
+      - Create a pull request with a detailed change summary
+      - Link the PR to the relevant issue
+      - Move the task to completed
     inputs:
-      - 最终重构分支
-      - 任务文件
+      - Final refactoring branch
+      - Task file
     outputs:
-      - 拉取请求
-      - 已完成的任务文件（位于 .agent-workspace/completed/）
+      - Pull request
+      - Completed task file (stored in .agents/workspace/completed/)

package/templates/.agents/workflows/refactoring.zh-CN.yaml

@@ -151,4 +151,4 @@ steps:
       - 任务文件
     outputs:
       - 拉取请求
-      - 已完成的任务文件（位于 .agent-workspace/completed/）
+      - 已完成的任务文件（位于 .agents/workspace/completed/）

package/templates/{.agent-workspace → .agents/workspace}/README.md

@@ -5,7 +5,7 @@ This directory is the runtime workspace for multi-AI collaboration. All contents
 ## Directory Structure
 
 ```
-.agent-workspace/
+.agents/workspace/
   active/           # Currently active tasks and handoff documents
   blocked/          # Tasks that are blocked and waiting for resolution
   completed/        # Completed tasks (kept for reference)

package/templates/{.agent-workspace → .agents/workspace}/README.zh-CN.md

@@ -5,7 +5,7 @@
 ## 目录结构
 
 ```
-.agent-workspace/
+.agents/workspace/
   active/           # 当前活跃的任务和交接文档
   blocked/          # 被阻塞的任务，等待解决
   completed/        # 已完成的任务（保留供参考）

package/templates/.claude/CLAUDE.md

@@ -88,56 +88,10 @@ Co-Authored-By: Claude <noreply@anthropic.com>
 
 ## Slash Commands
 
-### Development
-```bash
-/commit [message]           # Commit code
-/create-pr [branch]         # Create PR
-```
-
-### Task Management
-```bash
-/create-task <description>  # Create task from description
-/import-issue <number>      # Import GitHub Issue as task
-/analyze-task <task-id>     # Analyze task requirements
-/plan-task <task-id>        # Design technical plan
-/implement-task <task-id>   # Implement task
-/review-task <task-id>      # Code review
-/complete-task <task-id>    # Complete task
-/check-task <task-id>       # Check status
-/block-task <task-id>       # Block task
-/refine-task <task-id>      # Handle review feedback
-```
-
-### PR and Sync
-```bash
-/sync-issue <number>        # Sync progress to Issue
-/sync-pr <number>           # Sync progress to PR
-```
-
-### Testing and Release
-```bash
-/test                       # Run tests
-/test-integration           # Run integration tests
-/release <version>          # Version release
-/create-release-note        # Generate release notes
-```
+Available commands are auto-discovered from `.claude/commands/`. Type `/` in the prompt to see the full list with descriptions.
 
-### Security
-```bash
-/import-dependabot <number> # Import Dependabot alert
-/close-dependabot           # Close Dependabot alert
-/import-codescan <number>   # Import Code Scanning alert
-/close-codescan             # Close Code Scanning alert
-```
-
-### Tools
-```bash
-/init-milestones            # Initialize GitHub Milestones
-/init-labels                # Initialize GitHub Labels
-/refine-title               # Reformat Issue/PR title
-/upgrade-dependency         # Upgrade dependency
-/update-agent-infra  # Update AI collaboration config
-```
+For task workflow, the typical sequence is:
+`/create-task` -> `/analyze-task` -> `/plan-task` -> `/implement-task` -> `/review-task` -> `/complete-task`
 
 ## Language Conventions
 
@@ -153,20 +107,28 @@ Co-Authored-By: Claude <noreply@anthropic.com>
 This project supports Claude Code, Codex, Gemini CLI, OpenCode.
 
 - `.agents/` - Shared collaboration config
-- `.agent-workspace/` - Task workspace (git-ignored)
+- `.agents/workspace/` - Task workspace (git-ignored)
 
 **Collaboration guide**: `.agents/README.md`
 
 ## Skill Authoring Conventions
 
-When writing or updating `.agents/skills/*/SKILL.md` files, keep step numbering consistent:
+When writing or updating `.agents/skills/*/SKILL.md` files and their templates, keep step numbering consistent:
 
 1. Use consecutive integers for top-level steps: `1.`, `2.`, `3.`.
 2. Use nested numbering only for child actions that belong to a parent step: `1.1`, `1.2`, `2.1`.
-3. Use `a`, `b`, and `c` markers for branches, conditions, or alternative paths within the same step.
+3. Use `a`, `b`, and `c` markers for subordinate options, conditional branches, or parallel possibilities within the same step; use them only for in-step expansion, not for naming standalone decision paths or output templates.
 4. Do not use intermediate numbers such as `1.5` or `2.5`; if a new standalone step is needed, renumber the following top-level steps.
 5. When renumbering, update every in-document step reference so the instructions remain accurate.
 6. Extract long bash scripts into a sibling `scripts/` directory; the SKILL.md should contain only a single-line invocation (e.g., `bash .agents/skills/<skill>/scripts/<script>.sh`) and a brief summary of the script's responsibilities.
+7. In SKILL.md files and their `reference/` templates, when a standalone conditional flow, decision path, or output template needs a label, use "Scenario" naming (for example, use "Scenario A").
+
+### SKILL.md Size Control
+
+- Keep the SKILL.md body within about 500 tokens (roughly 80 lines / 2KB).
+- Move content beyond that threshold into a sibling `reference/` directory.
+- Use explicit navigation in the skeleton, such as: `Read reference/xxx.md before executing this step.`
+- Keep scripts in `scripts/` and execute them instead of inlining long bash blocks.
 
 <!-- Canonical source: .agents/README.md - keep in sync -->