sprint-planning

Generate sprint status tracking from project epic and story files.

4|2|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/anderson-0/mighty-powers --skill sprint-planning-anderson-0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-planning
Source: https://github.com/anderson-0/mighty-powers/tree/main/skills/sprint-planning
Command: npx skills add https://github.com/anderson-0/mighty-powers --skill sprint-planning-anderson-0

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the challenge of manually creating and maintaining sprint status tracking by transforming epic documentation into a structured development progress file.

Core Features & Use Cases

  • Epic Analysis and Status Generation: Parses epic files, extracts stories, and builds ordered sprint-status.yaml tracking structures.
  • Intelligent Progress Detection: Detects existing story files and preserves advanced statuses while validating workflow states.
  • Use Case: Development teams can generate a complete sprint tracking file from project epics and keep implementation progress synchronized across workflows.

Quick Start

Run sprint planning to generate a sprint status file from the project's epic documents.

Frequently Asked Questions about sprint-planning

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

FAQPage Schema
How do I generate sprint tracking YAML from epic documentation?

Sprint tracking YAML generation parses epic documentation to extract stories and builds an ordered sprint-status.yaml tracking structure. It intelligently detects existing story files to preserve advanced statuses while validating workflow states for software development planning.

What is the best way to maintain agile workflow status tracking for epics and stories?

Maintaining agile workflow status tracking involves transforming project epic documentation into a structured development progress file. This approach applies intelligent progress detection to preserve existing story states and keep implementation synchronized across development workflows.

Can I preserve existing story management statuses when regenerating sprint planning files?

Yes, you can preserve existing story management statuses when regenerating sprint planning files. The process intelligently detects existing story files, preserves advanced story statuses, and validates workflow state transitions to maintain development progress continuity.

How does epic parsing detect implementation progress for sprint planning?

Epic parsing detects implementation progress by analyzing project epic documentation and extracting story files to build ordered tracking structures. It validates workflow states and preserves existing development state transitions to ensure accurate sprint status generation.

Do I need specific dependencies to generate a sprint-status.yaml file from epics?

No specific dependencies are required to generate a sprint-status.yaml file from epics. The workflow independently parses epic files, extracts stories, and applies YAML status generation to build the structured development progress tracking file.