Sample specification
See exactly what you get.
This is a complete Build Specification for a made-up company: a construction firm that wants a simple app to track the tools going in and out of its tool room. The company, its people and their answers are invented. The structure is the real thing.
Inside the specification
Tool Room Tracker, in ten sections.
- 1
Build Readiness and Coverage Statement
How ready the spec is by fixed checks, anything still open, and what the experts were and weren't asked about.
- 2
The problem and the goal
The problem statement, the business objectives, and what's in and out of scope.
- 3
People
Who contributed, and the user roles in the application.
- 4
Requirements
Everything the application must do, each with a trace ID.
- 5
Disagreements and decisions
Where the experts disagreed, what was decided and by whom, and any open questions or assumptions.
- 6
Data and connected systems
The information the application keeps, how it relates, and the other systems it connects to.
- 7
Checks and tests
User stories, and the acceptance checks for each item.
- 8
Ownership
Who owns the application once it's built, settled before the build starts.
- 9
Traceability
Where every item came from, back to the expert answers behind it.
- 10
Approval record
Which items are approved, and who signed off and when.
The build package
What a developer or AI coding tool works from.
The specification is for the people who approve it. The build package is for whoever builds it. It comes as one zip file:
BUILD_PACKAGE.md
The whole package as one readable file. The place to start.
build-package.json
Everything in structured form, with a trace ID on every piece, plus build-package.schema.json, the published schema it follows.
specification.md
The specification itself, so the package stands on its own.
tools/AGENTS.md
Step-by-step instructions for any AI coding tool: the boundaries, the build sequence, the checks to automate, and when to stop and ask.
tools/CLAUDE.md
The same instructions, for tools that read a CLAUDE.md file.
Optional guard
An opt-in safety net for tools that support command hooks. It refuses things like skipping the project's safety checks, overwriting the main branch, or committing files that hold passwords.
When something in the package is missing or unclear, the instructions tell the builder to ask, not guess.
Want one of these for your idea?
Founding price $2,100 through March 31, 2027 or the first 50 specs; price after: $3,500. Tell us what you want to build, and we'll reply by email.