| name | playbook-orchestration |
| description | The wave-based workflow that coordinates the book's agent team (architect, theory-researcher, gh-aw-explorer, chapter-author, code-verifier, chapter-reviewer, frontend-builder) to produce the GitHub Agentic Workflows interactive book end to end. Use to plan and run the production pipeline for one or more chapters. |
Playbook Orchestration
This skill describes how the book's agents work together to build the GitHub Agentic Workflows
(gh-aw) 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 |
|---|
playbook-architect | Designs TOC, chapter specs, navigation, wave plan |
theory-researcher | Produces cited concept briefs from the gh-aw docs |
gh-aw-explorer | Installs & explores the gh aw CLI + schema; feature notes + examples |
chapter-author | Weaves theory + capability into chapter content |
code-verifier | Compiles every example workflow; 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
playbook-architect → TOC, chapter table, section breakdowns, wave plan.
