What problem does it solve? Academic writing projects spread progress across outlines, claim ledgers, evidence manifests, review cycles, and build outputs, making it hard to know where the paper stands or what to do next. This Skill reads all of those artifacts in one pass and produces a single honest status report with exactly one recommended next action. ## Core Features & Use Cases - Whole-flow status board: Tallies per-section, per-figure, and per-table states from the outline, claim coverage by ledger status, evidence freshness against upstream stamps, reference counts, and review-cycle state. - Deterministic signals: Runs read-only script modes (import.sh --diff for evidence drift, lint.sh --no-build for the build gate) and reports missing data as "unknown" rather than guessing. - One prioritized next action: Applies a fixed priority order (story, outline, evidence, drafting, audits, review, packaging) to name exactly one follow-up command, with red lint gates outranking everything. - Use Case: After a week of drafting, run the status check to see that two sections are still skeletons, three claims are unsourced, and the evidence has drifted — and receive the single command to run next. ## Quick Start Ask the assistant to run /stage-flow-status to show where the paper currently stands and what to work on next.
