The library ships 38 bundles. Each one is a document type with a template, a guide, a worked example, and a logged research trail. Every number on this page is read from manifest.json at build time.
All of them are beta, which in this library means researched and gate-checked: the structure and the sourcing have been checked, and whether the document helps anyone has not been measured.
| Bundle |
Phase |
Sizes |
Summary |
| Status Report |
undefined |
lean, full |
The periodic document that tells people who are not doing the work where a piece of work stands: what changed,… |
| Bundle |
Phase |
Sizes |
Summary |
| Architecture Decision Record |
develop |
lean, full |
Records one architecturally significant decision: the forces that made it necessary, the options genuinely con… |
| Request for Comments |
develop |
lean, full |
Proposes a change and gathers input before the decision is made: the motivation, the proposal, the alternative… |
| Software Design Document |
develop |
lean, full |
Describes how a system will be built: the technical design, its structure, the alternatives weighed, and the c… |
| Spike Report |
develop |
lean |
The written output of a time-boxed technical investigation: the uncertainty being reduced, what was actually t… |
| Bundle |
Phase |
Sizes |
Summary |
| Acceptance Criteria |
deliver |
lean, full |
Defines the conditions a user story must satisfy to be accepted, so “done” is verifiable and shared rather tha… |
| Announcement / Internal Comms |
deliver |
lean |
The message that tells the people in an organization who did not do the work that something is launching or ch… |
| Change Request |
deliver |
lean, full |
The record that gets a documented decision, made by one named person or body, about whether an already-agreed… |
| Epic |
deliver |
lean, full |
A named body of work large enough to need splitting into stories, written to carry what a tracker’s own epic r… |
| Product Backlog |
deliver |
lean, full |
The single, ordered, emergent list of work for a product, in service of a Product Goal: what the team might do… |
| Product Requirements Document |
deliver |
lean, full |
Defines what to build, for whom, and why, with scope and success criteria, so a team can design and build the… |
| Release Notes |
deliver |
lean, full |
Communicates what changed in a release to users and stakeholders, so people know what is new, what to do, and… |
| Sprint Backlog |
deliver |
lean, full |
The Developers’ living plan for a single Sprint: the Sprint Goal (why), the Product Backlog items selected for… |
| User Story |
deliver |
lean, full |
Describes a unit of work from the user’s perspective (“as a [user], I want [goal], so that [benefit]”) so a te… |
| Bundle |
Phase |
Sizes |
Summary |
| Business Case |
discover |
lean, full |
The document that justifies an investment before anyone commits to making it: what problem it solves, what it… |
| Project Brief |
discover |
lean, full |
The document that asks a named approver for authority to start finding out whether and how to proceed, before… |
| User Persona |
discover |
lean, full |
The document that says who a product is being built for, grounded in user research rather than in invention. L… |
| Bundle |
Phase |
Sizes |
Summary |
| Change Log |
undefined |
lean, full |
The standing register of every change requested against an agreed baseline and what was decided about each one… |
| Issue Log |
undefined |
lean, full |
The living, owned record of problems that have already happened on a project or program and need someone above… |
| KPI Dashboard |
undefined |
lean, full |
The defined set of key performance indicators an organization watches to know whether it is making progress to… |
| RAID Log |
undefined |
lean, full |
One working document that tracks the four kinds of open item on a project: Risks (might happen), Assumptions (… |
| Risk Register |
undefined |
lean, full |
The single, maintained record of the risks to an objective: what could happen, how likely and how damaging, wh… |
| Bundle |
Phase |
Sizes |
Summary |
| Incident Postmortem |
iterate |
lean, full |
The document a team writes after an incident to explain why it happened and what will change so it does not ha… |
| Project Milestone Retrospective |
iterate |
lean, full |
The document a team writes when a bounded piece of work has ended, for readers who may not have been there: wh… |
| Sprint Retrospective Notes |
iterate |
lean |
The written record of a Sprint Retrospective: what the team says went well, what it says needs to improve, and… |
| Bundle |
Phase |
Sizes |
Summary |
| Bug Report |
develop |
lean, full |
The document that gets one defect fixed by someone who was not there: what you did, what you expected, what ha… |
| Test Case |
develop |
lean, full |
The specification of one verification: what must be true before it runs, what is done, and what must happen as… |
| Test Plan |
develop |
lean, full |
The prospective document that scopes and prioritizes a testing effort: what is being tested and what is explic… |
| Test Summary Report |
develop |
lean, full |
The retrospective document that closes a testing effort: what was tested and on which build, what the testing… |
| Bundle |
Phase |
Sizes |
Summary |
| Definition of Done |
undefined |
lean, full |
The standard every increment is judged against, agreed once by a team and then consulted repeatedly rather tha… |
| Definition of Ready |
undefined |
lean |
The agreement a team makes about how complete a backlog item has to be before it can be pulled into a sprint:… |
| Launch Coordination Checklist |
undefined |
lean, full |
The standing list a team consults before it ships an externally visible change, so that readiness does not dep… |
| Production Readiness Review |
undefined |
lean, full |
The standing checklist a reviewing team consults, and a service’s own team fills in, before responsibility for… |
| Runbook |
undefined |
lean, full |
The document a responder opens when a known alert fires, so that the response does not depend on who is awake…. |
| Bundle |
Phase |
Sizes |
Summary |
| OKRs |
undefined |
lean, full |
The document that states what measurable change a team expects in this period and whether it got it. One quali… |
| Product Roadmap |
undefined |
lean, full |
The document that says in what order this product intends to solve the problems its strategy chose, and how ce… |
| Product Strategy |
undefined |
lean, full |
The document that says which problems this product will solve to reach its vision, and which it will not. It i… |
| Product Vision |
undefined |
lean, full |
The document that says what future this product is trying to create, for whom, and why this team is the one to… |