Book Orchestration
This skill describes how the book agents work together to build the Agent Package Manager (APM)
interactive book. It is the orchestration layer: who is dispatched, in what order, with what
hand-offs and checkpoints. (This is a starting scaffold — refine as the project evolves.)
The team
| Agent |
Role |
book-architect |
Designs TOC, chapter specs, navigation, wave plan |
theory-researcher |
Produces cited concept briefs from APM docs |
apm-cli-explorer |
Installs & introspects the apm CLI; feature notes + examples |
chapter-author |
Weaves theory + CLI reference into chapter content |
code-verifier |
Runs/validates every example; reports pass/fail |
chapter-reviewer |
Reviews chapters; ACCEPT/REVISE + ranked findings |
frontend-builder |
Builds the interactive HTML shell and wires content in |
Pipeline (per the case-study methodology: draft → review → revise, in waves)
Phase 0 — Architecture
- Dispatch
book-architect → TOC, chapter table, section breakdowns, wave plan.
- Dispatch
frontend-builder → scaffold the site shell + nav driven by the TOC.
- Checkpoint: commit TOC + shell.
Phase 1 — Environment
- Run the
apm-environment-setup skill (via apm-cli-explorer) → the apm CLI installed and
introspectable, plus a sample project to inspect.
Waves (repeat per wave; start with ONE pilot chapter, then widen)
For each chapter in the wave, run research in parallel, then author, verify, review:
5. Research (parallel):
theory-researcher → concept brief (content/research/<ch>-theory.md)apm-cli-explorer → feature notes + draft examples (content/research/<ch>-reference.md)
- Author:
chapter-author → chapter draft, pulling both briefs together.
- Verify:
code-verifier → validate/run every example; loop with author/explorer until all PASS
(or SKIPPED-needs-network with a clear marker).
- Review:
chapter-reviewer → ACCEPT or REVISE; on REVISE, route must-fixes to chapter-author.
- Integrate:
frontend-builder → wire the accepted chapter into the site nav.
- Checkpoint: commit the chapter (draft + examples + review verdict).
Integration pass (after all waves)
chapter-reviewer reads across chapters for cross-chapter consistency (terminology, ordering,
duplicate/contradictory claims).chapter-author applies cross-cutting fixes; frontend-builder finalizes nav/cross-links.
Wave ordering guidance
- Wave 0: one pilot chapter (e.g. "Why a package manager for agents?") to validate the pipeline.
- Wave 1: chapters with the most existing source material (lowest risk).
- Wave 2: the hardest chapters (governance/policy, transitive MCP, enterprise ramp).
- Wave 3: integration chapters needing cross-references to earlier ones.
Orchestration principles
- One chapter, one author per wave — keep scope inside an agent's context budget; split if too big.
- Checkpoint discipline — draft → review → revise → commit at each chapter.
- Batch reviews in later waves (one reviewer over several chapters) to cut dispatch overhead.
- Fix the primitives, not the symptom — when a recurring gap appears, update the relevant agent
definition / instructions rather than hand-patching each chapter.
- Verify before ship — no chapter is "done" until its examples PASS and the reviewer ACCEPTs.
1---2name: book-orchestration3description: The wave-based workflow that coordinates the book agent team (book-architect, theory-researcher, apm-cli-explorer, chapter-author, code-verifier, chapter-reviewer, frontend-builder) to produce the APM interactive book end to end. Use to plan and run the production pipeline for one or more chapters.4---56# Book Orchestration78This skill describes **how the book agents work together** to build the Agent Package Manager (APM)9interactive book. It is the orchestration layer: who is dispatched, in what order, with what10hand-offs and checkpoints. (This is a starting scaffold — refine as the project evolves.)1112## The team13| Agent | Role |14|-------|------|15| `book-architect` | Designs TOC, chapter specs, navigation, wave plan |16| `theory-researcher` | Produces cited concept briefs from APM docs |17| `apm-cli-explorer` | Installs & introspects the `apm` CLI; feature notes + examples |18| `chapter-author` | Weaves theory + CLI reference into chapter content |19| `code-verifier` | Runs/validates every example; reports pass/fail |20| `chapter-reviewer` | Reviews chapters; ACCEPT/REVISE + ranked findings |21| `frontend-builder` | Builds the interactive HTML shell and wires content in |2223## Pipeline (per the case-study methodology: draft → review → revise, in waves)2425### Phase 0 — Architecture261. Dispatch `book-architect` → TOC, chapter table, section breakdowns, wave plan.272. Dispatch `frontend-builder` → scaffold the site shell + nav driven by the TOC.283. Checkpoint: commit TOC + shell.2930### Phase 1 — Environment314. Run the `apm-environment-setup` skill (via `apm-cli-explorer`) → the `apm` CLI installed and32 introspectable, plus a sample project to inspect.3334### Waves (repeat per wave; start with ONE pilot chapter, then widen)35For each chapter in the wave, run **research in parallel**, then author, verify, review:365. **Research (parallel):**37 - `theory-researcher` → concept brief (`content/research/<ch>-theory.md`)38 - `apm-cli-explorer` → feature notes + draft examples (`content/research/<ch>-reference.md`)396. **Author:** `chapter-author` → chapter draft, pulling both briefs together.407. **Verify:** `code-verifier` → validate/run every example; loop with author/explorer until all PASS41 (or SKIPPED-needs-network with a clear marker).428. **Review:** `chapter-reviewer` → ACCEPT or REVISE; on REVISE, route must-fixes to `chapter-author`.439. **Integrate:** `frontend-builder` → wire the accepted chapter into the site nav.4410. Checkpoint: commit the chapter (draft + examples + review verdict).4546### Integration pass (after all waves)4711. `chapter-reviewer` reads across chapters for cross-chapter consistency (terminology, ordering,48 duplicate/contradictory claims).4912. `chapter-author` applies cross-cutting fixes; `frontend-builder` finalizes nav/cross-links.5051## Wave ordering guidance52- **Wave 0:** one pilot chapter (e.g. "Why a package manager for agents?") to validate the pipeline.53- **Wave 1:** chapters with the most existing source material (lowest risk).54- **Wave 2:** the hardest chapters (governance/policy, transitive MCP, enterprise ramp).55- **Wave 3:** integration chapters needing cross-references to earlier ones.5657## Orchestration principles58- **One chapter, one author per wave** — keep scope inside an agent's context budget; split if too big.59- **Checkpoint discipline** — draft → review → revise → commit at each chapter.60- **Batch reviews** in later waves (one reviewer over several chapters) to cut dispatch overhead.61- **Fix the primitives, not the symptom** — when a recurring gap appears, update the relevant agent62 definition / instructions rather than hand-patching each chapter.63- **Verify before ship** — no chapter is "done" until its examples PASS and the reviewer ACCEPTs.
webmaxru