gaia-epic-status

Aggregate epic statuses from Markdown and YAML into a read-only progress dashboard.

2|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/gaiastudio-ai/gaia-public --skill gaia-epic-status
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gaia-epic-status
Source: https://github.com/gaiastudio-ai/gaia-public/tree/main/plugins/gaia/skills/gaia-epic-status
Command: npx skills add https://github.com/gaiastudio-ai/gaia-public --skill gaia-epic-status

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

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.

Frequently Asked Questions about gaia-epic-status

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

FAQPage Schema
How do I view epic progress across multiple epics in a single dashboard?▼

To view epic progress, you can generate a read-only epic progress dashboard that aggregates per-epic totals, done counts, and completion percentages from epics-and-stories.md and sprint-status.yaml. It renders a Markdown table summarizing all epics.

How does epic status aggregation work when sprint-status.yaml is missing?▼

Epic status aggregation gracefully handles missing sprint-status.yaml by deriving individual story statuses directly from per-story Markdown frontmatter. It computes epic totals and completion percentages without writing to any source files.

Can I filter the epic progress dashboard to show a single epic key like E28?▼

Yes, you can filter the epic progress dashboard to a single epic key like E28. This focused view calculates and presents the completion data, status distributions, and totals for that specific epic only.

What statuses are tracked in the per-status distributions for agile epics?▼

The per-status distributions for agile epics track backlog, ready-for-dev, in-progress, review, done, and blocked. The dashboard aggregates these statuses to show per-epic totals and completion percentages.

Does the epic progress dashboard modify sprint-status.yaml or story files?▼

No, the epic progress dashboard is strictly read-only and never writes to sprint-status.yaml, epics-and-stories.md, or any story files. It guarantees no writes to source artifacts while computing status data.

How are epics with zero stories handled in the progress dashboard?▼

Epics with zero stories are handled in the progress dashboard by rendering their totals as 0 / 0 (---) with a blank completion percentage. This read-only view correctly handles empty epics without errors.