execute-sprint

Create dependency-ordered tasks from sprint tickets and delegate work to programmer agents.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/Busboom-Foo/meetupfu --skill execute-sprint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: execute-sprint
Source: https://github.com/Busboom-Foo/meetupfu/tree/main/.claude/skills/execute-sprint
Command: npx skills add https://github.com/Busboom-Foo/meetupfu --skill execute-sprint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill coordinates sprint execution by turning tickets into executable tasks and enabling parallel work through isolated programmer teammates using per-ticket git worktrees.

Core Features & Use Cases

  • Dependency-aware task creation: builds tasks from sprint tickets and enforces their dependencies so only unblocked work begins.
  • Parallel execution with worktrees: spawns programmer teammates who operate in separate git worktrees branched from the sprint branch.
  • Guaranteed completion & merge back: validates tests and acceptance criteria, marks tickets done, and merges worktrees back to the sprint branch.

Quick Start

Acquire the execution lock, ensure an active sprint with tickets, and trigger the sprint execution workflow to spawn programmers and create tasks.

Frequently Asked Questions about execute-sprint

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

FAQPage Schema
How do I automate sprint ticket execution with parallel git worktrees?

Automate sprint ticket execution by creating tasks from tickets and delegating work to programmer agents. The tool spawns isolated git worktrees branched from the sprint branch, enabling parallel development across multiple tickets simultaneously.

How does dependency-based task ordering work for sprint execution?

Dependency-based task ordering builds tasks from sprint tickets and enforces their dependencies, ensuring only unblocked work begins. This prevents programmer agents from starting tickets that rely on incomplete upstream tasks within the sprint branch.

What's the best way to merge parallel worktrees back into a sprint branch?

Merging worktrees back into the sprint branch is handled automatically after tests and acceptance criteria are validated. The tool marks ticket frontmatter as done and merges each isolated worktree sequentially to preserve branch integrity.

Do I need an active sprint with tickets before triggering parallel worktree development?

An active sprint with tickets and a sprint branch is required before triggering execution. You must also acquire the execution lock to coordinate programmer agents and ensure dependency-aware task creation starts correctly.

Can I use git worktrees for parallel development without manual branch switching?

Git worktrees enable parallel development without manual branch switching by spawning programmer teammates in separate worktrees. Each teammate operates in isolation branched from the sprint branch, validating tests before merging back.

Why does sprint execution validate tests before updating ticket frontmatter?

Sprint execution validates tests to guarantee completion criteria are met before updating ticket frontmatter to done. This ensures only passing work is merged from worktrees back into the sprint branch, maintaining codebase stability.