plan-sprint

Plan sprint roadmaps and detailed artifacts with usecases, architecture updates, and tickets.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill creates a structured two-phase sprint planning workflow: an initial roadmap phase for batch planning and a detail phase for full artifacts, enabling predictable planning outcomes with clear guardrails.

Core Features & Use Cases

  • Two-phase planning: Roadmap (batch) followed by Detail (one sprint at a time) to produce lightweight sprint.md and full planning artifacts.
  • Artifact generation: Phase 2 outputs include usecases.md, architecture-update.md, and tickets, with inline architecture review.
  • Guardrails: Enforces that tickets are not created during roadmap mode and branches are created only after acquiring the execution lock.

Quick Start

Run the plan-sprint workflow to generate roadmap and detailed planning artifacts for upcoming sprints.

Frequently Asked Questions about plan-sprint

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

FAQPage Schema
How does two-phase sprint planning work for agile roadmaps?

Two-phase sprint planning separates batch roadmap creation from single-sprint detailing, generating lightweight sprint.md files first, then full artifacts like usecases and architecture updates for one sprint at a time.

How do I generate sprint tickets and use cases from a roadmap?

To generate sprint tickets and use cases, run the detail phase on a single sprint from your roadmap, which outputs usecases.md, architecture-update.md, and tickets with inline architecture review.

Can I create tickets during the roadmap phase of sprint planning?

No, tickets are not created during the roadmap phase. The workflow enforces guardrails that prevent ticket generation until you enter the detail phase for a specific sprint.

When are git branches created during the sprint planning workflow?

Git branches are created only after acquiring the execution lock, ensuring branch creation happens at the point of actual execution commitment rather than during planning.

Do I need a design overview document for sprint roadmap planning?

Yes, the workflow uses docs/clasi/design/overview.md as a design reference to guide the generation of sprint roadmaps, usecases, architecture updates, and tickets.

What artifacts are produced by detailed sprint planning?

Detailed sprint planning produces usecases.md, architecture-update.md with inline architecture review, and tickets, providing full planning artifacts to guide execution of a single sprint.