Templates
Documents we actually use, with the instruction notes left in. Every template is Markdown — open it anywhere, paste it into whatever your organisation uses, keep it in version control.
Project Plan
A project plan that stays useful after week one — scope boundary, milestones with exit criteria, dependencies with owners, and a decision log.
BRD
A BRD structure that survives delivery — measurable objectives, atomic testable requirements, and an out-of-scope section that prevents arguments later.
Test Plan
A test plan with real entry and exit criteria, risk-based prioritisation, and an environment section — the three things most test plans skip.
SOP
An SOP structure someone can actually follow under pressure — numbered steps, decision points, what to do when it goes wrong, and a named owner with a review date.
Architecture Diagram
A four-diagram starter set based on the C4 approach, plus the conventions that make diagrams readable — including the one that matters most, saying what each arrow means.
Security Checklist
A pre-release security checklist ordered by what actually gets exploited — identity and access first, then data, then dependencies, then the AI-specific surface.
QA Checklist
A quality gate to run before sign-off — covering the non-functional areas that get skipped under deadline pressure and cost the most to retrofit.
Release Checklist
What must be true before you ship — with a rollback that has been tested rather than assumed, and a go/no-go with a named decision-maker.
Incident Report
A blameless incident report that produces actual fixes — timeline, contributing factors rather than a single cause, and actions with owners and dates.