Engineering Playbook
A set of commands and guides for structuring development workflows, architectural decisions, code reviews, and team operations.
Built on two complementary frameworks:
- The Preamble - How teams think together (peer collaboration, correctness over agreement)
- Design Rules - What teams build toward (clarity, simplicity, resilience, extensibility)
Every command in the playbook assumes both. Every workflow integrates both.
Start Here
Want the thinking, not the commands? Read The Playbook - five chapters on how teams think together, what they build toward, and how to adopt it. About thirty minutes cover to cover.
New to the playbook? Read Why We Build Playbooks for the full philosophy, or jump to Getting Started for a scenario-based introduction.
Looking for a specific command? Browse the sidebar by category, or use search (press S).
Adopting for your team? See the Adoption Guide for team-size-specific paths.
Not using Claude Code? See Using With Other Tools for adaptation guides.
How It Works
The playbook provides a three-step daily ritual:
scope → code → review
Scope captures what you’re building. You code without interruptions. Review checks your work against relevant quality perspectives and commits when it passes.
Beyond the daily ritual, the playbook includes planning tools, architecture patterns, multi-perspective review workflows, deployment guides, incident response, and team operations.
See Workflows for the full picture, or Recipes for real-world examples.
Browse by Category
Use the sidebar to explore commands organized by workflow sequence within each category: Core, Development, Planning, Reviews, Deployment, Repo, Templates, Utilities, and People.
The Integration Guide shows how commands compose into workflows.