aped-sprint

Orchestrate parallel story dispatch into per-story worktrees within an APED project.

2|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/yabafre/aped-claude --skill aped-sprint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aped-sprint
Source: https://github.com/yabafre/aped-claude/tree/main/src/templates/skills/aped-sprint
Command: npx skills add https://github.com/yabafre/aped-claude --skill aped-sprint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

APED sprint dispatch coordinates parallel story execution so teams can start multiple feature branches at once without breaking ordering, dependencies, or workflow ownership.

Core Features & Use Cases

  • Parallel sprint dispatch orchestration: starts multiple story worktrees under a fixed sprint umbrella branch and queues the correct first prompt for each story leader.
  • Robust state-driven planning: validates state integrity, computes dependency buckets (ready/blocked), checks capacity, and enforces “exactly one active epic” at a time.
  • Ticket-system aware pre-checks and post-dispatch sync: performs read-only ticket validation before dispatch, then assigns and transitions ticket statuses after worktrees exist.

Quick Start

Use aped-sprint when you want to run an APED “parallel sprint” and dispatch ready stories for the currently selected epic into separate worktrees.

Frequently Asked Questions about aped-sprint

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

FAQPage Schema
How do I run parallel feature branches for multiple stories without breaking dependencies?

Parallel sprint dispatch provisions per-story git worktrees under a single sprint umbrella, computing dependency buckets to ensure only ready stories start while blocked stories wait, preserving execution order across branches.

What is a git worktree dispatch workflow for parallel epic execution?

Git worktree dispatch creates isolated working directories for each story within an epic, allowing simultaneous development across multiple branches while enforcing exactly one active epic and validating state integrity before provisioning begins.

Does parallel sprint dispatch require a specific git branch state to start?

Parallel sprint dispatch enforces main-root only execution, meaning it must run from the main branch. It also performs worktree safety checks and state integrity validation before creating any new feature worktrees.

How do I sync ticket statuses when dispatching parallel story worktrees?

Ticket dispatch performs read-only ticket validation before creating worktrees, then assigns and transitions ticket statuses after the feature worktrees exist, delegating story status transitions to downstream workflow handlers.

Can I start multiple parallel sprints at the same time for different epics?

Parallel sprint dispatch enforces exactly one active epic at a time. It validates state integrity and checks capacity limits to ensure safe parallel execution within that single epic before provisioning worktrees.

Who handles code review and merging after parallel sprint dispatch creates the worktrees?

Parallel sprint dispatch delegates review and merge control to separate workflow stages, while it focuses solely on worktree provisioning, dependency readiness checks, and initial prompt queuing for each story leader.