What problem does it solve? When working through a multi-chapter, multi-phase book-building pipeline, it is hard to remember which chapter is in progress, which phases passed or failed, and what to do next. This Skill reads the project's tracking files and prints a single consolidated status report. ## Core Features & Use Cases - Progress table: Renders one compact table from progress.json showing every chapter's phase status (analyze, curate, design, implement, verify, review, viz, notebook, knowledge, publish) with pass/running/fail/blocked/todo markers. - Current-chapter detail: Surfaces the verdict, open items, viz summary, and must-fix list from the current chapter's verification, viz, and review reports, each trimmed to eight lines. - Environment and git check: Reports Python and package versions, chapter text split state, Jupyter kernel registration, recent commits, working tree cleanliness, remote sync, and GitHub Pages availability. - Use Case: After returning to the fluidpy project, run /status to see that chapter 2 failed verification, review its must-fix items, and get the exact /do-chapter command to resume. ## Quick Start Run /status to print the full project progress table, current chapter issues, environment state, and the recommended next command.