sprint-planning

Extract epics and stories from epic files to generate sprint status tracking files.

Updated Jan 29, 2026
One-click install
npx skills add https://github.com/GuidoBergman/aegish --skill sprint-planning-guidobergman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-planning
Source: https://github.com/GuidoBergman/aegish/tree/main/.claude/skills/sprint-planning
Command: npx skills add https://github.com/GuidoBergman/aegish --skill sprint-planning-guidobergman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the generation and management of sprint status tracking files, ensuring all epics and stories are accounted for and their progress is accurately monitored throughout the development lifecycle.

Core Features & Use Cases

  • Epic and Story Extraction: Gathers all epics and stories from designated epic files.
  • Status Tracking: Monitors the development lifecycle status of each item.
  • Use Case: Streamline your agile development process by automatically updating your sprint board and generating status reports based on the latest information from your epics and stories.

Quick Start

Load the core workflow and execute the sprint planning configuration.

Frequently Asked Questions about sprint-planning

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

FAQPage Schema
How do I automate sprint status tracking for epics and stories?

Sprint planning automation works by loading a core workflow XML and executing a specified workflow YAML configuration. It processes these configurations to extract epics and stories, generating detailed task management files.

Can I use YAML configurations to manage agile story management workflows?

Yes, YAML configurations are used to manage story management workflows. The Skill processes specific YAML files to extract stories from epics and monitor their development lifecycle status within Phase 4 implementation workflows.

What is the best way to extract epics and stories from epic files for sprint planning?

Extracting epics and stories requires loading a core workflow XML file first. Once loaded, you execute a specified workflow YAML configuration to process the epic files and generate the sprint status tracking outputs.

Do I need to load a core workflow XML before executing sprint planning configurations?

Yes, loading a core workflow XML is required before executing sprint planning configurations. The core workflow provides the necessary foundation to process the specified workflow YAML for detailed task management.

Does sprint planning work with Phase 4 implementation workflows?

Yes, sprint planning supports Phase 4 implementation workflows by processing specific YAML configurations. It monitors the development lifecycle status of stories and epics extracted from your designated epic files.