execute-sprint

Assign sprint tickets to programmer agents in isolated worktrees.

1|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/busboom-software-studio/design-trainer --skill execute-sprint-busboom-software-studio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: execute-sprint
Source: https://github.com/busboom-software-studio/design-trainer/tree/main/.claude/skills/execute-sprint
Command: npx skills add https://github.com/busboom-software-studio/design-trainer --skill execute-sprint-busboom-software-studio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Executes sprint tickets by creating Tasks for a team of programmer agents working in parallel worktrees.

Core Features & Use Cases

  • Create Tasks for each ticket with metadata including sprint ID and ticket ID
  • Spawn programmer teammates who work in isolated worktrees per ticket
  • Coordinate dependency resolution so only unblocked tickets start

Quick Start

Start the sprint by spawning programmer teammates and assigning tickets to isolated worktrees.

Frequently Asked Questions about execute-sprint

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

FAQPage Schema
How do I execute sprint tickets in parallel using isolated git worktrees?

To execute sprint tickets in parallel, you can assign tasks to programmer agents who work in isolated git worktrees. This orchestrates sprint execution by creating tasks with sprint and ticket IDs, managing dependencies so only unblocked tickets start.

What is the best way to manage parallel programmer agents for task management?

Managing parallel programmer agents involves spawning teammates and assigning tickets to isolated worktrees. The system coordinates dependency resolution automatically, ensuring only unblocked tickets begin execution while tracking ticket state across the team.

How does dependency-aware task creation work for sprint ticket tracking?

Dependency-aware task creation works by evaluating ticket dependencies before execution starts. Only unblocked tickets are assigned to programmer agents in isolated worktrees, preventing merge conflicts and ensuring sprint tickets proceed in the correct order.

Can I coordinate multiple programmer agents working in separate worktrees simultaneously?

Yes, you can coordinate multiple programmer agents working in separate worktrees simultaneously. The sprint execution system spawns programmer teammates, assigns each to an isolated worktree per ticket, and manages parallel execution with test validation.

Do I need to manually resolve ticket dependencies before starting parallel sprint execution?

No, you do not need to manually resolve ticket dependencies before starting. The system coordinates dependency resolution automatically during sprint execution, ensuring only unblocked tickets are assigned to programmer agents working in isolated git worktrees.

Why use isolated git worktrees for parallel sprint ticket execution instead of branches?

Isolated git worktrees provide each programmer agent with a separate working directory per ticket during sprint execution. This enables true parallel task management without worktree interference, applying test validation before completing ticket state management.