sprint-dev

Coordinate dependency-driven sprint execution with AI agents and approval gates.

Updated Mar 10, 2026

Search Tags:#orchestration #code-review #sprint #ai-agents #dependency #wave-based #avfl

Ready to run

npx skills add https://github.com/iamsteveholmes/momentum --skill sprint-dev-iamsteveholmes

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sprint-dev
Source: https://github.com/iamsteveholmes/momentum/tree/main/skills/momentum/skills/sprint-dev
Command: npx skills add https://github.com/iamsteveholmes/momentum --skill sprint-dev-iamsteveholmes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sprint execution often stalls due to manual coordination between dependencies, approvals, and multi-phase quality gates. This skill orchestrates parallel AI agents to drive dependency-driven development and post-merge AVFL while maintaining traceability and resume capabilities.

Core Features & Use Cases

Dependency-driven sprint execution: automatic spawning of dev agents as stories become unblocked.
Integrated AVFL and team-review workflows: post-merge quality scanning and parallel verification.
Resumable sessions and dedup guards: safe recovery after crashes and prevention of duplicate spawns.

Quick Start

Invoke the sprint-dev skill to start Phase 1 by loading the active sprint from sprints/index.json and begin dependency-driven development.

Frequently Asked Questions about sprint-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate sprint execution with AI agents and dependency-driven story sequencing?▼

Automated sprint execution coordinates parallel AI agents to spawn development tasks as dependencies clear. It applies wave-based story sequencing to manage parallel agent workflows, ensuring stories only start once their upstream dependencies are resolved.

What is wave-based story sequencing in dependency-driven sprint orchestration?▼

Wave-based story sequencing is a dependency-driven scheduling method that groups stories into execution waves. Stories in the same wave run in parallel via AI agents, while subsequent waves wait for upstream dependencies and approval gates to pass before spawning.

How do I handle crash recovery and duplicate AI agent spawns during a sprint?▼

Resumable sessions and spawn-de-duplication guards handle crash recovery and prevent duplicate agent spawns. The orchestration system tracks active story states, allowing safe session resumption and automatically blocking redundant dev agent creation after interruptions.

Can I integrate post-merge code reviews and AVFL scanning into automated sprint workflows?▼

Yes, post-merge AVFL and team-review workflows integrate directly into the sprint orchestration. After story merges, the system triggers automated AVFL quality scanning and parallel verification, coordinating team reviews through defined approval gates.

How do I start an automated sprint delivery phase using a sprint index file?▼

To start Phase 1, invoke the sprint orchestration skill to load your active sprint from the sprints/index.json file. This initializes dependency-driven development, reads story states, and begins spawning dev agents for unblocked stories immediately.

What are the limitations of using AI agents for dependency-driven sprint orchestration?▼

This orchestration approach relies on a valid sprints/index.json file and structured approval gates to function. Limitations include potential bottlenecks if manual approval gates are delayed, and the need for active fix queue handling when post-merge AVFL or team reviews fail.