Reference — generated from the toolkit
Source of truth: toolkit/templates/README.md. Edit it there; this page is regenerated on build.
Templates
Fillable artefact templates — copy one, fill it, commit the instance alongside the work it describes. The written standards that govern how each is used live in the handbook's Standards section (see the sidebar).
| Template | Used at | Governed by | Status |
|---|---|---|---|
adr.md | any significant decision | Decision records | v1 |
pfd.md | Definition | Acceptance criteria | v1 |
domain-brief.md | Definition | (domain-brief standard to follow) | v1 |
ux-flow.md | Design | Design Review gate | v1 |
data-model.md | Design | Design Review gate | v1 |
screen-spec.md | Design | Design Review gate | v1 |
runbook.md | Build / Production | Production Readiness gate | v1 |
risk-acceptance.md | STOP / any gate waiver | Remediation backlog | v1 |
legacy-knowledge-pack.md | STOP | Tech-debt audit | v1 |
tooling-scorecard.md | Tool selection | Tooling evaluation | v1 |
stack-playbook.md | Tech selection → Build | Tech-selection | v1 |
competitive-teardown.md | Definition (on demand) | Discovery & research | v1 |
test-plan.md | Design | Test strategy | v1 |
release-evidence-pack.md | Production | AI provenance | v1 |
incident-comms.md | Production / incidents | Rapid-fix SLAs | v1 |
squad-charter.md | Squad formation | Squad playbook | v1 |
demo-script.md | GTM / sales | Demo environment | v1 |
One artefact per concern; every instance is versioned in the repo it belongs to and written to be read by humans and agents.