Tooling for specification-driven work
TomSpecs is supported by tools that treat specifications as data: they read the structure, check it and change it through the model instead of through text editing.
Structured documents
Markdown documents that declare their schema and give every section a stable id. A validator checks a document against its schema; tools address sections by id.
The TomSpecs object model
A Dart model of every TomSpecs document type: which sections exist, which forms and lists they hold, which values are allowed. Documents are stored as YAML or Markdown and edited through it.
Specifications to code
A gate checks that a specification is complete, an extraction routes every section to the code areas it feeds, and authoring steps generate a skeletal application whose declarations cite their sources.
Tom AI extension
Editing, validating and reviewing specifications inside VS Code, a process view that walks a project through its phases and gates, and a prompt queue that hands the steps to AI agents.
Status
The method and the tools are developed and used inside the Tom framework workspace. Downloads, documentation and examples will follow on this site.