epic-statuslisted

Read-only progress dashboard over a wave-structured decomposition (one epic = one <backlog>/<task-name>/ directory from /prepare Phase 6): which subtasks are done/in-progress/blocked, which wave is current, the next safe wave to launch (all Deps merged, Owns pairwise disjoint), what can launch in parallel right now, and whether running parallel sessions collide on ownership. Where a parent RUN-ORDER exists it is read as the execution truth and reported against plan frontmatter as drift. Reports and recommends — never edits, commits, or launches. TRIGGER when: "where is this epic", "what's the next wave", "can I start these in parallel", "epic status", or before launching concurrent /implement sessions. TRIGGER ALSO on the same question phrased as plain work, with this skill unnamed — "how far along is <backlog>/<name>", "what's left in this epic", "which of these are safe to run at once", "did wave N land", "is this finished", "check if the epic is done? <backlog>/<name>". Those last two are cheap status ques
mik2win/foureyes · ★ 2 · AI & Automation · score 76

Install: claude install-skill mik2win/foureyes

# Epic Status: $ARGUMENTS A **strictly read-only** dashboard over one epic — a `<backlog>/<task-name>/` directory produced by `/prepare` Phase 6 (see `skills/prepare/reference/parallel-wave-execution.md` for the wave model this skill reads). It answers: where does the epic stand, which wave is current, what is the **next safe wave**, and do any running sessions **collide on ownership**. It changes nothing: statuses are stamped by `/implement` and reconciled by the user; this skill only reports and recommends. This skill carries only invariant logic. The backlog location and commands come from `.claude/PROJECT.md`. `Bash` is for read-only inspection (`git log`, `git status`, `ls`) — never mutation. ## Phase 0 — Load profile & resolve the epic 1. Read `.claude/PROJECT.md`. If missing or `profile_status: TEMPLATE`, fall back to the root `CLAUDE.md` (always in context) when it carries the backlog location and commands — note you're running without a kit profile — and only **STOP** → run `/bootstrap` first if *neither* has them. Resolve **Plans / backlog location** (and the **Archive on done** location, if any). 2. `$ARGUMENTS` names the epic — a directory under the backlog location, or its name. If empty, glob the backlog location for directories containing a `00-overview.md`, list them, and **ask** which epic to report on. Do not guess. 3. **Parent RUN-ORDER — look, never require.** Walk up from the epic directory toward the program directory for a `RUN-ORD