playbook-usagelisted

# Playbook Usage `pragmatic-engineer/playbook` is a Claude Code plugin: 13 slash commands under `/playbook:*` plus supporting skills and hooks. Its primary flow is a four-stage planning pipeline, `/playbook:brainstorm` then `/playbook:scope` or `/playbook:adr` then `/playbook:implement`, that takes a raw idea through a verified plan to delivered code. Some pipeline commands run the moment the intent matches, no confirmation asked; others only offer in one line and wait for a yes before doing anything (see Trigger phrases, below). ## Command reference ### Planning pipeline | Command | One-line purpose | When to reach for it | |---|---|---| | `/playbook:brainstorm` | Divergent discovery on a raw idea: challenges the premise, weighs 2-3 approaches, produces an approved PRD and design doc. | The direction is not settled yet: an idea seed, open-ended exploration, or genuine uncertainty about approach. | | `/playbook:scope` | Interview-driven planning that turns a settled direction into a verified implementation plan, its Work Units grouped into PR-sized Segments. | The direction is settled and the work needs a concrete plan to hand to `/playbook:implement`. | | `/playbook:adr` | Records a hard-to-reverse architectural decision as a fact-checked ADR, with an optional execution blueprint, saved to `docs/adr/`. | Choosing between named alternatives, a decision that is expensive to undo, or a request to document the reasoning behind a choice. | | `/playbook:implement` | Executes a