Build from decisions, not scattered context
Practical guides for writing software specifications, running a spec-driven workflow, and giving coding agents the context they actually need.
Field guide · 8 min
What is a living software specification?
Learn what makes a software specification living: structured decisions, explicit ownership, reviewable revisions, and direct access for people and coding agents.
Read the guide →Workflow · 9 min
Spec-driven development, without the ceremony
A practical spec-driven development workflow: define behavior, review decisions, give agents bounded context, implement, verify, and update the specification.
Read the guide →Template · 10 min
A product specification template teams can build from
A practical product specification template covering outcomes, scope, roles, flows, data models, permissions, acceptance tests, risks, and review decisions.
Read the guide →Agent context · 8 min
Using MCP to give coding agents product context
Learn how Model Context Protocol gives coding agents bounded product context, what to expose, and how to keep permissions and human approval intact.
Read the guide →Worked example
User authentication specification
See roles, flows, decisions, a typed data model, and acceptance cases assembled into one compact, illustrative specification.
Put the idea into a spec your team can use
Start with one feature. Structure the decisions, review the AI proposals, and publish a version your team and coding agents can query.
Start free