Playbooks
A playbook is a scenario from start to finish: what to do, in which order, which items apply and which templates to fill in. The same playbook is a page for people and an Agent Skill for coding agents.
For whom. Anyone starting a piece of work who wants the whole path, not a single rule.
What goes here. playbooks/<slug>.md with kind: playbook. A playbook references items by id and
templates by path; it does not restate their rules, so a rule always has one home. Its own rules are about
the process only: the order of stages, their entry and exit criteria, and who approves.
Available. Project foundation (mgmt.project-foundation): vision, requirements, research, blueprint,
decisions, roadmap and repository rules, with the project-foundation skill. Architecture review
(arch.architecture-review): as-is architecture, technical debt, risks, target and migration plan, with the
architecture-review skill.
Planned. Quality and Release (definitions of ready and done, test strategy, quality gates, deployment and rollback).