Team Playbook
A living document for how our team works. If something here is wrong or outdated, fix it — don't just complain about it.
How to use this doc
- New to the team? Read sections 1, 2, 3, and 11. Skim the rest.
- Looking up a process? Use the table of contents, or search the docs site:
docker compose -f site/compose.yml up -d --buildserves it on port 8080 (seesite/). - Disagree with something? Open a PR against this doc with the change.
- Working with an AI agent? The engineering conventions reach every product repository as agent context (an
AGENTS.mdblock andplaybook-*skills), synced by CI fromagent/. When you change a convention, update its skill in the same PR.
Table of Contents
- Team & Roles
- Working Cadence
- Backlog Management
- Task Workflow
- Definition of Done
- Code Standards
- Code Review
- Branching & Releases
- Observability
- Incidents & Postmortems
- Communication Norms
- Onboarding
- Tech Debt & Investment
- Security Basics
- Templates - PR, Postmortem, On-Call Handoff, Onboarding, Jira work item examples
Engineering conventions live in conventional/, copyable starting points in templates/.
Last updated: 2026-10-06. Found something wrong? Open a PR.