The method
A process with phases, artifacts and gates
TomSpecs defines the sequence from an initial idea to production code. Every phase has the same shape:
- Inputs - what must exist before the phase can begin
- Activities - the work, done by a person, an AI, or both
- Outputs - the artifacts it produces, each a structured document
- Quality gate - what must be true before the next phase starts
The phases
| # | Phase | Key output |
|---|---|---|
| 1 | Project Idea | Free-form vision and ideas (PI) |
| 2 | Solution Blueprint | A structured overview of the whole system (SBP) |
| 3 | Detailed Specifications | One structured document per concern (CLA, RSP, TOM, IFM, SAS, ATS, XDS, ISC, QAP, TRP) |
| 4 | CodeSpecs | A skeletal application: compiles, does not run yet |
| 5 | Test Derivation | Test cases derived from the specifications |
| 6 | Implementation | Working code and unit tests |
| 7 | Business Acceptance | Deployed, tested, accepted |
| 8 | Multi-Tenant | Provisioning and subscription integration (optional) |
Levels of specification
- Vision - why the system exists, whom it serves, what problem it solves
- Requirements - what it must do, and how well
- Architecture - components, boundaries and data flow
- Design - classes, interfaces and protocols of each component
- Implementation spec - exact behaviour and edge cases, precise enough for AI to generate code
- Test spec - what must be tested and what is expected
From documents to code
Project Idea --> Solution Blueprint --> Detailed Specifications
|
CodeSpecs gate
|
skeletal application <-- generated, with back-links to the spec sections
|
tests derived --> implementation --> acceptance