Back to Details

agile-workflow

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Agile Workflow Orchestrator

敏捷工作流编排器

A skill that guides agents through structured agile development workflows by intelligently invoking commands in sequence. Uses checkpoint-based flow control to auto-progress between steps while pausing at key decision points.
Note: This is a platform-agnostic, git-only workflow. For PR-based workflows with specific platforms, use:
  • gitea-workflow
    for Gitea repositories
  • github-agile
    for GitHub repositories
这是一项通过智能地按顺序调用命令，引导Agent完成结构化敏捷开发工作流的技能。它采用基于检查点的流程控制，在步骤间自动推进，同时在关键决策点暂停。
注意： 这是一个与平台无关、仅基于Git的工作流。如需针对特定平台且集成PR的工作流，请使用：
  • 针对Gitea仓库的
    gitea-workflow
  • 针对GitHub仓库的
    github-agile

When to Use This Skill

何时使用此技能

Use this skill when:
  • Starting work for the day ("run morning standup", "start my day")
  • Working on a task ("implement next task", "continue working")
  • Completing a development cycle ("finish this task", "prepare PR")
  • Running sprint ceremonies ("start sprint", "end sprint", "retrospective")
  • Resuming interrupted work ("what's next", "where was I")
Do NOT use this skill when:
  • Running a single specific command (use that command directly)
  • Just checking status (use 
    /status
    directly)
  • Only doing code review without full cycle (use 
    /review-code
    directly)
  • Researching or planning without implementation
在以下场景中使用此技能：
  • 开启当日工作（「运行晨间站会」「开启我的一天」）
  • 处理任务（「实现下一个任务」「继续工作」）
  • 完成开发周期（「完成此任务」「准备PR」）
  • 执行迭代仪式（「启动迭代」「结束迭代」「回顾会议」）
  • 恢复中断的工作（「下一步做什么」「我之前做到哪了」）
请勿在以下场景中使用此技能：
  • 仅运行单个特定命令（直接使用该命令即可）
  • 仅检查状态（直接使用
    /status
    ）
  • 仅进行代码评审而不执行完整周期（直接使用
    /review-code
    ）
  • 仅进行研究或规划而不涉及实现

Prerequisites

前置条件

Before using this skill:
  • Git repository initialized with worktree support
  • Context network with backlog structure at 
    context-network/backlog/
  • Task status files at 
    context-network/backlog/by-status/*.md
使用此技能前需满足：
  • 已初始化支持worktree的Git仓库
  • 上下文网络在
    context-network/backlog/
    路径下具备待办事项结构
  • 任务状态文件位于
    context-network/backlog/by-status/*.md

Workflow Types Overview

工作流类型概述

WORKFLOW TYPES
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

TASK CYCLE (Primary)     DAILY                SPRINT
──────────────────────   ──────────────────   ──────────────────
sync                     Morning:             Start:
  ↓                        sync --last 1d       sync --all
next → [CHECKPOINT]        status --brief       groom --all
  ↓                        groom --ready        plan sprint-goals
implement                                       status
  ↓                      Evening:
[CHECKPOINT]               checklist          End:
  ↓                        discovery            sync --sprint
review-code                sync --last 1d       retrospective
review-tests                                    audit --sprint
  ↓                                             maintenance --deep
[CHECKPOINT]
  ↓
apply-recommendations (if issues)
  ↓
merge-prep → [CHECKPOINT]
  ↓
merge-complete
  ↓
update-backlog & status
  ↓
END
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
WORKFLOW TYPES
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

TASK CYCLE (Primary)     DAILY                SPRINT
──────────────────────   ──────────────────   ──────────────────
sync                     Morning:             Start:
  ↓                        sync --last 1d       sync --all
next → [CHECKPOINT]        status --brief       groom --all
  ↓                        groom --ready        plan sprint-goals
implement                                       status
  ↓                      Evening:
[CHECKPOINT]               checklist          End:
  ↓                        discovery            sync --sprint
review-code                sync --last 1d       retrospective
review-tests                                    audit --sprint
  ↓                                             maintenance --deep
[CHECKPOINT]
  ↓
apply-recommendations (if issues)
  ↓
merge-prep → [CHECKPOINT]
  ↓
merge-complete
  ↓
update-backlog & status
  ↓
END
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

State Detection

状态检测

The skill determines current workflow state automatically. No manual tracking needed.
该技能会自动检测当前工作流状态，无需手动跟踪。

Detection Signals

检测信号

SignalHow to CheckIndicates
Worktree exists
git worktree list
Task in progress
Task branch active
git branch --show-current
matches 
task/*
Active implementation
Uncommitted changes
git status --porcelain
Active coding
Branch merged
git branch --merged main
Ready for cleanup
信号检查方式指示状态
Worktree存在
git worktree list
任务进行中
任务分支激活
git branch --show-current
匹配
task/*
正在实现
未提交变更
git status --porcelain
正在编码
分支已合并
git branch --merged main
准备清理

State Matrix

状态矩阵

STATE DETECTION LOGIC
─────────────────────────────────────────────────────────────
Check                           → State           → Next Step
─────────────────────────────────────────────────────────────
No worktree, no in-progress     → IDLE            → sync, next
Worktree exists, uncommitted    → IMPLEMENTING    → continue implement
Worktree exists, all committed  → READY_REVIEW    → review-code
Reviews complete, ready to merge→ MERGE_READY     → merge-prep
Branch merged, worktree exists  → CLEANUP         → merge-complete
─────────────────────────────────────────────────────────────
For detailed detection algorithms, see references/state-detection.md.
STATE DETECTION LOGIC
─────────────────────────────────────────────────────────────
Check                           → State           → Next Step
─────────────────────────────────────────────────────────────
No worktree, no in-progress     → IDLE            → sync, next
Worktree exists, uncommitted    → IMPLEMENTING    → continue implement
Worktree exists, all committed  → READY_REVIEW    → review-code
Reviews complete, ready to merge→ MERGE_READY     → merge-prep
Branch merged, worktree exists  → CLEANUP         → merge-complete
─────────────────────────────────────────────────────────────
如需了解详细的检测算法，请查看references/state-detection.md。

Invocation Patterns

调用方式

bash
undefined
bash
undefined

Auto-detect state and continue from where you are

自动检测状态并从当前位置继续

/agile-workflow
/agile-workflow

Start specific workflow phase

启动特定工作流阶段

/agile-workflow --phase task-cycle /agile-workflow --phase daily-morning /agile-workflow --phase daily-evening /agile-workflow --phase sprint-start /agile-workflow --phase sprint-end
/agile-workflow --phase task-cycle /agile-workflow --phase daily-morning /agile-workflow --phase daily-evening /agile-workflow --phase sprint-start /agile-workflow --phase sprint-end

Resume work on specific task

恢复特定任务的工作

/agile-workflow --task TASK-123
/agile-workflow --task TASK-123

Preview what would happen without executing

预览执行内容但不实际运行

/agile-workflow --dry-run
undefined
/agile-workflow --dry-run
undefined

Task Cycle Phase

任务周期阶段

The primary workflow for completing a single task from selection to merge.
这是从任务选择到合并完成的单个任务核心工作流。

Step 1: Sync Reality

步骤1：同步实际状态

Ensure context network matches actual project state.
Run: sync --last 1d --dry-run
Purpose: Detect drift between documented and actual state
Output: Sync report showing completions, partial work, divergences
确保上下文网络与项目实际状态一致。
运行：sync --last 1d --dry-run
目的：检测文档记录与实际状态的偏差
输出：显示完成情况、部分工作内容和差异的同步报告

Step 2: Select Task

步骤2：选择任务

Identify the next task to work on.
Run: next
Purpose: Find highest priority ready task
Output: Task ID, title, branch name suggestion
CHECKPOINT: TASK_SELECTED
  • Pause to confirm task selection
  • User can accept or choose different task
  • On accept: continue to implementation
确定接下来要处理的任务。
运行：next
目的：找到优先级最高的就绪任务
输出：任务ID、标题、分支名称建议
检查点：TASK_SELECTED
  • 暂停以确认任务选择
  • 用户可接受或选择其他任务
  • 确认后：进入实现阶段

Step 3: Implement

步骤3：实现

Test-driven development in isolated worktree.
Run: implement [TASK-ID]
Purpose: Create worktree, write tests first, implement, verify
Output: Working implementation with passing tests
CHECKPOINT: IMPL_COMPLETE
  • Pause after implementation completes
  • Show test results and coverage
  • On success: continue to review
在独立的worktree中进行测试驱动开发。
运行：implement [TASK-ID]
目的：创建worktree，先编写测试，再实现功能，最后验证
输出：可正常运行且测试通过的实现代码
检查点：IMPL_COMPLETE
  • 实现完成后暂停
  • 显示测试结果和覆盖率
  • 成功后：进入评审阶段

Step 4: Review

步骤4：评审

Quality validation of implementation.
Run: review-code --uncommitted
Run: review-tests --uncommitted
Purpose: Identify quality issues, security concerns, test gaps
Output: Review reports with issues and recommendations
CHECKPOINT: REVIEWS_DONE
  • Display combined review results
  • If critical issues: must address before continuing
  • If no issues: auto-continue to PR prep
  • User decides: apply recommendations now or defer
对实现内容进行质量验证。
运行：review-code --uncommitted
运行：review-tests --uncommitted
目的：识别质量问题、安全隐患和测试缺口
输出：包含问题和建议的评审报告
检查点：REVIEWS_DONE
  • 展示合并后的评审结果
  • 若存在严重问题：必须解决后才能继续
  • 若无问题：自动进入PR准备阶段
  • 用户可决定：立即应用建议或延后处理

Step 5: Apply Recommendations (Conditional)

步骤5：应用建议（可选）

Address review findings intelligently.
Run: apply-recommendations [review-output]
Purpose: Apply quick fixes now, defer complex changes to tasks
Output: Applied fixes + created follow-up tasks
智能处理评审发现的问题。
运行：apply-recommendations [review-output]
目的：立即应用快速修复，将复杂变更延后至后续任务
输出：已应用的修复内容 + 创建的后续任务

Step 6: Prepare Merge

步骤6：准备合并

Validate and prepare for merge to main.
Run: merge-prep
Purpose: Validate implementation, run final checks, prepare for merge
Output: Ready to merge to main
CHECKPOINT: MERGE_READY
  • Display validation results
  • Show files that will be merged
  • On all checks pass: continue to merge
  • On failure: stop, address issues
验证并准备合并至主分支。
运行：merge-prep
目的：验证实现内容，运行最终检查，为合并做准备
输出：已准备好合并至主分支
检查点：MERGE_READY
  • 展示验证结果
  • 显示即将合并的文件
  • 所有检查通过后：进入合并阶段
  • 若失败：停止并解决问题

Step 7: Complete Merge

步骤7：完成合并

Merge to main and cleanup.
Run: merge-complete
Purpose: Merge to main, delete branch, remove worktree, update status
Output: Task marked complete, cleanup done
合并至主分支并清理资源。
运行：merge-complete
目的：合并至主分支，删除分支，移除worktree，更新状态
输出：任务标记为完成，清理完成

Step 8: Update Backlog and Project Status

步骤8：更新待办事项和项目状态

Persist progress to source-of-truth documentation.
Run: Part of merge-complete (Phase 6)
Purpose: Update epic file (task → complete), unblock dependents, update project status
Output: Backlog and project status reflect actual progress
Why this step matters: Without it, completed tasks remain marked "ready" in backlog files and project status stays stale. Internal tracking files are session-scoped; the backlog and status files are the persistent source of truth.
For detailed task-cycle instructions, see references/phases/task-cycle.md.
将进度持久化到可信的文档源中。
运行：属于merge-complete的一部分（第6阶段）
目的：更新史诗文件（任务→完成），解除依赖阻塞，更新项目状态
输出：待办事项和项目状态反映实际进度
此步骤的重要性： 若跳过此步骤，已完成的任务会在待办文件中仍标记为「就绪」，项目状态也会过时。内部跟踪文件仅在会话范围内有效，待办事项和状态文件是持久化的可信源。
如需了解详细的任务周期说明，请查看references/phases/task-cycle.md。

Daily Phase

日常工作阶段

Quick sequences for start and end of workday.
适用于工作日开始和结束的快速流程。

Morning Standup (~5 min)

晨间站会（约5分钟）

Run sequence:
1. sync --last 1d --dry-run   # What actually happened yesterday
2. status --brief --sprint    # Current sprint health
3. groom --ready-only         # What's ready to work on

Output: Clear picture of today's priorities
运行序列：
1. sync --last 1d --dry-run   # 昨天实际完成的工作
2. status --brief --sprint    # 当前迭代健康状况
3. groom --ready-only         # 可立即处理的任务

输出：清晰的今日优先级视图

Evening Wrap-up (~10 min)

晚间收尾（约10分钟）

Run sequence:
1. checklist                  # Ensure nothing lost
2. discovery                  # Capture learnings
3. sync --last 1d            # Update task statuses

Output: Knowledge preserved, state synchronized
For detailed daily instructions, see references/phases/daily.md.
运行序列：
1. checklist                  # 确保没有遗漏事项
2. discovery                  # 记录学习内容
3. sync --last 1d            # 更新任务状态

输出：知识得以保留，状态保持同步
如需了解详细的日常工作说明，请查看references/phases/daily.md。

Sprint Phase

迭代阶段

Ceremonies for sprint boundaries.
适用于迭代起止的仪式流程。

Sprint Start (~60 min)

迭代启动（约60分钟）

Run sequence:
1. sync --all                 # Full reality alignment
2. groom --all               # Comprehensive grooming
3. plan sprint-goals         # Architecture and goals
4. status --detailed         # Baseline metrics

Output: Sprint plan with groomed, ready backlog
运行序列：
1. sync --all                 # 全面对齐实际状态
2. groom --all               # 全面梳理待办事项
3. plan sprint-goals         # 确定架构和目标
4. status --detailed         # 记录基线指标

输出：包含已梳理就绪待办事项的迭代计划

Sprint End (~90 min)

迭代结束（约90分钟）

Run sequence:
1. sync --sprint             # Final sprint sync
2. retrospective             # Capture learnings
3. audit --scope sprint      # Quality review
4. status --metrics          # Sprint metrics
5. maintenance --deep        # Context network cleanup

Output: Sprint closed, learnings captured, ready for next
For detailed sprint instructions, see references/phases/sprint.md.
运行序列：
1. sync --sprint             # 迭代最终同步
2. retrospective             # 记录学习内容
3. audit --scope sprint      # 质量评审
4. status --metrics          # 迭代指标
5. maintenance --deep        # 上下文网络清理

输出：迭代已关闭，学习内容已记录，准备进入下一个迭代
如需了解详细的迭代说明，请查看references/phases/sprint.md。

Checkpoint Handling

检查点处理

Checkpoints are pauses for human decision-making.
检查点是供人工决策的暂停节点。

Checkpoint Behavior

检查点行为

At each checkpoint:
  1. Summarize what just completed
  2. Show key results and any issues
  3. Present next steps
  4. Wait for user input
在每个检查点：
  1. 总结刚刚完成的内容
  2. 展示关键结果和所有问题
  3. 呈现下一步计划
  4. 等待用户输入

Checkpoint Responses

检查点响应

ResponseAction
"continue" / "proceed" / "yes"Move to next step
"stop" / "pause"Save state, exit workflow
"back"Re-run previous step
"skip"Skip current step (use cautiously)
Custom inputMay adjust next step parameters
响应操作
"continue" / "proceed" / "yes"进入下一步
"stop" / "pause"保存状态，退出工作流
"back"重新运行上一步
"skip"跳过当前步骤（谨慎使用）
自定义输入可能调整下一步参数

Auto-Continue Conditions

自动继续条件

Some checkpoints can auto-continue when conditions are met:
CheckpointAuto-Continue If
IMPL_COMPLETEAll tests pass, build succeeds
REVIEWS_DONENo critical or high severity issues
MERGE_READYAll validation checks pass
For detailed checkpoint handling, see references/checkpoint-handling.md.
满足特定条件时，部分检查点可自动继续：
检查点自动继续条件
IMPL_COMPLETE所有测试通过，构建成功
REVIEWS_DONE无严重或高优先级问题
MERGE_READY所有验证检查通过
如需了解详细的检查点处理说明，请查看references/checkpoint-handling.md。

Command Reference

命令参考

Each workflow step uses embedded command instructions:
CommandReferencePurpose
syncreferences/commands/sync.mdReality synchronization
groomreferences/commands/groom.mdTask refinement
nextreferences/commands/next.mdTask selection
implementreferences/commands/implement.mdTDD implementation
review-codereferences/commands/review-code.mdCode quality review
review-testsreferences/commands/review-tests.mdTest quality review
apply-recommendationsreferences/commands/apply-recommendations.mdTriage and apply fixes
merge-prepreferences/commands/merge-prep.mdMerge preparation
merge-completereferences/commands/merge-complete.mdMerge and cleanup
discoveryreferences/commands/discovery.mdLearning capture
retrospectivereferences/commands/retrospective.mdPost-work analysis
maintenancereferences/commands/maintenance.mdContext network cleanup
每个工作流步骤都使用嵌入式命令说明：
命令参考文档目的
syncreferences/commands/sync.md同步实际状态
groomreferences/commands/groom.md梳理任务
nextreferences/commands/next.md选择任务
implementreferences/commands/implement.mdTDD实现
review-codereferences/commands/review-code.md代码质量评审
review-testsreferences/commands/review-tests.md测试质量评审
apply-recommendationsreferences/commands/apply-recommendations.md分类处理并应用修复
merge-prepreferences/commands/merge-prep.md合并准备
merge-completereferences/commands/merge-complete.md合并与清理
discoveryreferences/commands/discovery.md记录学习内容
retrospectivereferences/commands/retrospective.md事后分析
maintenancereferences/commands/maintenance.md上下文网络清理

Example: Complete Task Cycle

示例：完整任务周期

Scenario: Start of day, implement next available task
Invocation:
/agile-workflow --phase task-cycle
Flow:
Agent: Detecting current state...
       No worktree found, checking ready tasks...

Agent: Running sync --last 1d --dry-run
       [Sync output: 0 tasks completed but undocumented]

Agent: Running next
       Found: TASK-042 - Add user preferences endpoint
       Priority: High | Size: Small | Branch: task/TASK-042-preferences

       ╔═══════════════════════════════════════════╗
       ║  CHECKPOINT: Task Selection               ║
       ╠═══════════════════════════════════════════╣
       ║  Selected: TASK-042                       ║
       ║  Proceed with implementation?             ║
       ║                                           ║
       ║  [continue] [stop] [other task]           ║
       ╚═══════════════════════════════════════════╝

User: continue

Agent: Creating worktree at .worktrees/TASK-042/
       Running implement TASK-042
       [Implementation proceeds with TDD...]

       Tests: 12 passing
       Coverage: 87%
       Build: Success

       ╔═══════════════════════════════════════════╗
       ║  CHECKPOINT: Implementation Complete      ║
       ╠═══════════════════════════════════════════╣
       ║  All tests passing, ready for review      ║
       ║  Proceed to code review?                  ║
       ║                                           ║
       ║  [continue] [stop]                        ║
       ╚═══════════════════════════════════════════╝

[Flow continues through review, merge...]
场景： 工作日开始，实现下一个可用任务
调用：
/agile-workflow --phase task-cycle
流程：
Agent: 正在检测当前状态...
       未找到worktree，检查就绪任务...

Agent: 运行sync --last 1d --dry-run
       [同步输出：0个已完成但未记录的任务]

Agent: 运行next
       找到：TASK-042 - 添加用户偏好设置端点
       优先级：高 | 规模：小 | 分支：task/TASK-042-preferences

       ╔═══════════════════════════════════════════╗
       ║  CHECKPOINT: Task Selection               ║
       ╠═══════════════════════════════════════════╣
       ║  已选择：TASK-042                       ║
       ║  是否继续实现？             ║
       ║                                           ║
       ║  [continue] [stop] [other task]           ║
       ╚═══════════════════════════════════════════╝

User: continue

Agent: 在.worktrees/TASK-042/创建worktree
       运行implement TASK-042
       [按TDD流程进行实现...]

       测试：12项通过
       覆盖率：87%
       构建：成功

       ╔═══════════════════════════════════════════╗
       ║  CHECKPOINT: Implementation Complete      ║
       ╠═══════════════════════════════════════════╣
       ║  所有测试通过，准备进入评审      ║
       ║  是否继续进行代码评审？                  ║
       ║                                           ║
       ║  [continue] [stop]                        ║
       ╚═══════════════════════════════════════════╝

[流程继续进行评审、合并...]

Limitations

局限性

  • Requires context network with specific backlog structure
  • Git-only workflow (no PR integration - for PR workflows use gitea-workflow or github-agile)
  • Single-task focus (parallel task work not orchestrated)
  • Best suited for solo development or trusted team direct-to-main workflows
  • 需要具备特定待办事项结构的上下文网络
  • 仅基于Git的工作流（无PR集成 - 如需PR工作流请使用gitea-workflow或github-agile）
  • 专注于单任务处理（不编排并行任务工作）
  • 最适合独立开发或信任团队的直接合并至主分支工作流

Related Skills

相关技能

  • gitea-workflow - For Gitea repositories with PR integration
  • github-agile - For GitHub repositories with PR integration
  • skill-maker - Create new skills following agentskills.io spec
  • research-workflow - For research tasks before implementation
  • gitea-workflow - 适用于集成PR的Gitea仓库
  • github-agile - 适用于集成PR的GitHub仓库
  • skill-maker - 按照agentskills.io规范创建新技能
  • research-workflow - 适用于实现前的研究任务