do-chapter

Orchestrates a multi-agent pipeline converting a textbook chapter into tested Python code, notebooks, and interactive explainers.

Updated Sep 13, 2026
One-click install
npx skills add https://github.com/shammun/fluidpy --skill do-chapter-shammun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: do-chapter
Source: https://github.com/shammun/fluidpy/tree/main/.claude/skills/do-chapter
Command: npx skills add https://github.com/shammun/fluidpy --skill do-chapter-shammun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Producing a complete learning package for one chapter of a fluid mechanics textbook (analysis, curated coverage, tested Python functions, a teaching notebook, and 4-5 interactive HTML explainers) requires coordinating many specialized agents, quality gates, and publish steps, which is error-prone to do by hand. ## Core Features & Use Cases - Phased autonomous pipeline: Runs analyze, curate, design, implement, verify, review, viz, notebook, knowledge, and publish phases with gates, fix loops, and a commit per phase. - Parallel subagent orchestration: Launches design and implementation together, then review, per-explainer viz builders, and the notebook builder concurrently, with merge gates and retry limits. - Resumable progress tracking: Tracks phase status in progress.json and supports --from, --only, --consult, and --no-push flags for partial or supervised runs. - Use Case: Run /do-chapter 7 to turn Chapter 7 (Gravity Waves) of Kundu's Fluid Mechanics into verified fluidpy functions, an executed teaching notebook, five interactive explainers, and a published GitHub Pages update. ## Quick Start Ask the assistant to run /do-chapter 7 to execute the full chapter pipeline, or use /do-chapter 7 --from viz to resume from the explainer-building phase.

Frequently Asked Questions about do-chapter

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

FAQPage Schema
How do I run the full chapter pipeline for one chapter?

Run /do-chapter N where N is the chapter number, for example /do-chapter 7. The orchestrator reads book.yaml and progress.json, then executes analyze through publish phases with gates and a commit per phase.

How do I resume a chapter pipeline after a crash?

Use /do-chapter N --from PHASE to resume from a specific phase; all earlier phases must already be marked pass or done in progress.json. A phase left in running state is re-run from its start, treating on-disk artifacts as inputs only.

Can I run only one phase of the chapter pipeline?

Yes, use /do-chapter N --only PHASE to execute just that phase and its gate. You can also add --consult to pause for user approval after the curation shortlist, or --no-push to skip the final git push.

What happens when the verification phase fails?

The orchestrator sends failing items back to the implementer agent and re-runs the math verifier, up to three rounds. If failures persist, the phase is marked fail, the pipeline stops, and nothing downstream runs on unverified code.

What are the limitations of the do-chapter pipeline?

It processes one chapter per session and requires the previous chapter to be fully published first. It is specific to the fluidpy repository structure, depends on its tools and agents, and never publishes fewer than four passing explainers.