# Engineering team template

Built for **software and product engineering teams** that want architecture decisions, runbooks, incidents, and retrospectives searchable beside onboarding material.

## Target audience

- Tech leads documenting **ADRs and runbooks** without a separate wiki
- SRE and platform engineers standardizing **incident** and **deploy** practice
- Engineering managers capturing **retro** outcomes with traceable action items

## Folder layout

| Folder | Purpose |
|--------|---------|
| `inbox/` | New-hire orientation pointers |
| `architecture/` | ADRs for APIs, data models, and cross-cutting concerns |
| `runbooks/` | Step-by-step operational procedures |
| `incidents/` | Post-incident notes and reusable templates |
| `retrospectives/` | Sprint or milestone retros with commitments |
| `onboarding/` | Checklists and first-week expectations |

Use consistent `project` values in frontmatter (team or service name). Sample content uses `2026-04-07` as a reference date.