A useful place
to start building.
Free software specification templates with requirements, acceptance criteria and the decisions that still need an answer. Download a working file or adapt one in Build Brief.
Restaurant ordering system specification
An ordering system connects several workflows that have to agree: the customer’s basket, the payment record, the kitchen queue and the manager’s view of a location. This specification template starts with five restaurants and makes those boundaries explicit before implementation.
Markdown · CSV · JSON · Coding-agent task02 / Access, revision history and explicit approvalClient portal requirements template
A client portal is useful when a team can tell which delivery a comment refers to, who may see a file and whether a client has actually approved a revision. This template follows a design studio from sharing the first delivery to recording an explicit approval.
Markdown · CSV · JSON · Coding-agent task03 / Source provenance, retrieval and AI boundariesResearch library software specification
An internal research library should make earlier work findable without losing the original source or exposing restricted documents. This template starts with a team that captures notes and attachments, searches previous work and may add source-linked AI suggestions later.
Markdown · CSV · JSON · Coding-agent taskWhat belongs in a software specification?
A useful specification describes who the software serves, the outcome it needs to produce, the workflow, testable requirements and the boundaries of the first release. It also records decisions that remain unresolved. These templates give you a concrete starting point without silently filling in your budget, timeline or approval.
The guided files are available without an account or an AI request. They contain proposals for review. You can edit them in your own tools, import the JSON into Build Brief, or use the requirements as the starting point for an engineering conversation.