jwynia/agent-skills/agile-workflow
Claude Code and agent skill by jwynia/agent-skills
- community
Checking that the SKILL.md file is still in the repository.
Orchestrate agile development workflows by invoking commands in sequence with checkpoint-based flow control. This skill should be used when the user asks to 'run the workflow', 'continue working', 'what's next', 'complete the task cycle', 'start my day', 'end the sprint', 'implement the next task', or wants guided step-by-step development assistance. Platform-agnostic git-only workflow without PR integration. Keywords: workflow, orchestrate, agile, task cycle, sprint, daily, implement, review, merge, standup, retrospective, git.
Install
npx vskill@latest install jwynia/agent-skills/agile-workflowSKILL.md
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-workflowfor Gitea repositoriesgithub-agilefor GitHub repositories
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
/statusdirectly) - Only doing code review without full cycle (use
/review-codedirectly) - Researching or planning without implementation
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
Workflow Types Overview
State Detection
The skill determines current workflow state automatically. No manual tracking needed.
Detection Signals
| Signal | How to Check | Indicates | |
|---|---|---|---|
| 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 |
State Matrix
For detailed detection algorithms, see references/state-detection.md.
Invocation Patterns
Task Cycle Phase
The primary workflow for completing a single task from selection to merge.
Step 1: Sync Reality
Ensure context network matches actual project state.
Step 2: Select Task
Identify the next task to work on.
CHECKPOINT: TASK_SELECTED
- Pause to confirm task selection
- User can accept or choose different task
- On accept: continue to implementation
Step 3: Implement
Test-driven development in isolated worktree.
CHECKPOINT: IMPL_COMPLETE
- Pause after implementation completes
- Show test results and coverage
- On success: continue to review
Step 4: Review
Quality validation of implementation.
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
Step 5: Apply Recommendations (Conditional)
Address review findings intelligently.
Step 6: Prepare Merge
Validate and prepare for 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
Step 7: Complete Merge
Merge to main and cleanup.
Step 8: Update Backlog and Project Status
Persist progress to source-of-truth documentation.
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.
Daily Phase
Quick sequences for start and end of workday.
Morning Standup (~5 min)
Evening Wrap-up (~10 min)
For detailed daily instructions, see references/phases/daily.md.
Sprint Phase
Ceremonies for sprint boundaries.
Sprint Start (~60 min)
Sprint End (~90 min)
For detailed sprint instructions, see references/phases/sprint.md.
Checkpoint Handling
Checkpoints are pauses for human decision-making.
Checkpoint Behavior
At each checkpoint:
- Summarize what just completed
- Show key results and any issues
- Present next steps
- Wait for user input
Checkpoint Responses
| Response | Action | |
|---|---|---|
| "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 input | May adjust next step parameters |
Auto-Continue Conditions
Some checkpoints can auto-continue when conditions are met:
| Checkpoint | Auto-Continue If | |
|---|---|---|
| IMPL_COMPLETE | All tests pass, build succeeds | |
| REVIEWS_DONE | No critical or high severity issues | |
| MERGE_READY | All validation checks pass |
For detailed checkpoint handling, see references/checkpoint-handling.md.
Command Reference
Each workflow step uses embedded command instructions:
| Command | Reference | Purpose | |
|---|---|---|---|
| sync | references/commands/sync.md | Reality synchronization | |
| groom | references/commands/groom.md | Task refinement | |
| next | references/commands/next.md | Task selection | |
| implement | references/commands/implement.md | TDD implementation | |
| review-code | references/commands/review-code.md | Code quality review | |
| review-tests | references/commands/review-tests.md | Test quality review | |
| apply-recommendations | references/commands/apply-recommendations.md | Triage and apply fixes | |
| merge-prep | references/commands/merge-prep.md | Merge preparation | |
| merge-complete | references/commands/merge-complete.md | Merge and cleanup | |
| discovery | references/commands/discovery.md | Learning capture | |
| retrospective | references/commands/retrospective.md | Post-work analysis | |
| maintenance | references/commands/maintenance.md | Context network cleanup |
Example: Complete Task Cycle
Scenario: Start of day, implement next available task
Invocation:
Flow:
This is the start of the file. Read the full SKILL.md on GitHub.
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/tech/development/workflow/agile-workflow/SKILL.md
Popularity
- Repository stars
- 33
- Repository forks
- 7
- 7-day trend score
- 18
Stars and forks are for the whole GitHub repository, not this skill alone. Refreshed 18 Mar 2026, 7 months ago.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/jwynia/agent-skills/agile-workflow)