What problem does it solve? Coordinating a repeatable outcome across multiple Personas, Skills, Tools, and artifacts requires an explicit operating model; without one, stages, ownership, state, and failure recovery stay implicit and unverifiable. ## Core Features & Use Cases - Playbook Composition: Design a new reusable Playbook with ordered stages, entry/exit criteria, owners, shared state, decision rights, quality gates, and failure recovery paths. - Update and Repair: Compare a requested change against an existing Playbook, return the smallest change set, or inspect a Playbook for defects in stage contracts, gates, and evidence without silently rewriting it. - Use Case: When a job-search workflow needs repeatable stages for intake, application packet drafting, review, and submission with named approvers and fallback behavior, use this Skill to compose the Playbook contract before any run begins. ## Quick Start Use $playbook-composer to design a reusable Playbook for my multi-stage review workflow with defined owners, handoffs, and quality gates.