playbook-usagelisted

# Playbook Usage `pragmatic-engineer/playbook` is a Claude Code plugin: 12 slash commands under `/playbook:*` plus supporting skills and hooks. Its primary flow is a planning pipeline, `/playbook:plan` (its own divergent phase settles the direction, then converges on a verified plan) or `/playbook:adr` for a hard-to-reverse decision, 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:plan` | One continuous, interview-driven session from a raw idea to a verified implementation plan: opens divergent (challenges the premise, weighs 2-3 approaches) then converges into an interview for Work Units and Segments, its Work Units grouped into PR-sized Segments. | Any planning need, whether the direction is still open (an idea seed, open-ended exploration, genuine uncertainty about approach) or already settled (a defined feature ready for a plan): the session settles it either way before producing the 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 t