gaia-epic-status

What problem does it solve?

This Skill provides a read-only view of epic progress across multiple epics by aggregating data from docs/planning-artifacts/epics-and-stories.md and docs/implementation-artifacts/sprint-status.yaml. If sprint-status.yaml is unavailable, it gracefully derives statuses from the individual story Markdown frontmatter, avoiding any writes to source artifacts.

Core Features & Use Cases

• Read-only epic progress dashboard that summarizes per-epic completion data.
• Reads epics-and-stories.md and sprint-status.yaml to compute totals, done, and status distributions; if sprint-status.yaml is missing, derives story statuses from per-story files.
• Supports filtering to a single epic key (e.g., E28) for focused views.
• Handles epics with zero stories by rendering as 0 / 0 (---) and shows per-status distributions: backlog, ready-for-dev, in-progress, review, done, blocked.
• Never writes to sprint-status.yaml, epics-and-stories.md, or any story file.

Quick Start

Render the epic progress dashboard for all epics, or filter to a specific epic key (e.g., E28) to view its status.