What problem does it solve? When a development session spans epics, wave batches, or standalone runs, it is hard to answer "where do we stand" without trusting stale memory. This Skill re-reads the actual sources of truth — the epic ledger, issue tracker, git branches, and open PRs/MRs — and prints a read-only status report. ## Core Features & Use Cases - Role-aware reporting: Detects whether the session is a wave master, a batch worker, or a standalone run, and reads the appropriate sources for each. - Epic ledger reads: Fetches an epic's wave ledger via ledger.mjs and issue-slice.mjs, reporting batch rows, merge queues, gates, and outstanding user expectations. - Change request state: Reads PR/MR state and required checks on GitHub (gh) or GitLab (glab), including fork-aware merged-state detection. - Use Case: After restarting a session mid-epic, ask for the status and get a fresh report of which batches merged, which checks are pending, and what still needs your decision — with unread sources named explicitly rather than printed empty. ## Quick Start Ask the assistant "what's the status of epic #42" or simply "where do we stand" to get a fresh read-only report of the current work.
