From the first idea to running code - specified, traced, generated.
TomSpecs is a structured process for building software with AI. Every phase produces a typed specification document, every step passes a quality gate, and every line of generated code can be traced back to the requirement it implements.
Why specifications first
An AI writes code quickly, and just as quickly writes the wrong code. TomSpecs moves the decisions into documents that a person reviews and a machine can check, so the code that follows is the consequence of an agreed specification, not of a prompt.
Typed documents
Specifications are documents with a schema: every section has an id, every field a type. Tools read, validate and edit them, not just people.
Gates between phases
A phase ends only when its gate passes: the document is complete against its schema, its values are valid, its references resolve.
From requirement to code
Generated code cites the specification sections it comes from, so a change can be followed in both directions.
Built-in review rounds
Questions, comments and proposed changes live inside the documents, are answered there and are applied or rejected with a trail.
Eight phases
Each phase has defined inputs, activities, outputs and a quality gate. Details on the method page.
- Project IdeaFree-form vision and ideasPI
- Solution BlueprintA structured overview of the whole systemSBP
- Detailed SpecificationsOne structured document per concernCLA, RSP, TOM, IFM, SAS, ATS, XDS, ISC, QAP, TRP
- CodeSpecsA skeletal application: compiles, does not run yet
- Test DerivationTest cases derived from the specifications
- ImplementationWorking code and unit tests
- Business AcceptanceDeployed, tested, accepted
- Multi-TenantProvisioning and subscription integrationoptional