Tenders, e-mails, meeting notes and spreadsheets in. A traceable, BABOK-structured specification out — goals, requirements, use cases, rules and data, every item linked to the one above it. The source of truth for spec-driven development.
The requirements are spread across a tender, forty e-mails, three sets of meeting notes and a spreadsheet nobody owns. A specification written by hand from that takes weeks, and it is out of date the day something changes.
Coding agents now build straight from the specification. Every gap in it becomes a gap in the software, written fast and with confidence. The bottleneck is no longer the code. It is the spec.
Drop in what the project already has: tenders, PDFs, Word files, e-mails, spreadsheets, meeting notes.
Deus walks the BABOK path in six phases — from business need to one specification per use case.
Every module is structured and versioned. Refine it in plain language, approve it to lock it.
A requirement changes or a new document arrives: Deus shows what it touches and updates only that.
Export the whole specification — DOCX, PDF or Markdown — for your team and your coding agents.
Upload what the project already has. Deus extracts the text from each file, shows it to you, and tells you how much of it one analysis run reads.
One goal, six BABOK phases, run in the background step by step. Each step builds on the ids of the steps before it, so the result is one connected specification, not a pile of documents.
30 BABOK techniques, each with its own structure — stakeholders, functional and non-functional requirements, use cases, business rules, data model, data dictionary, interfaces and diagrams. Every change is a new version; approving a module locks it.
The chain from business need to use case specification is built from the modules themselves — no AI involved. The matrix shows coverage and gaps; the map draws every item with its links.
When something changes, Deus shows which modules it reaches and why. Sync edits only the items in scope instead of regenerating the module, checks the edit against the module’s structure, and saves it as a new version you can compare or revert.
A document that arrives after the specification exists is assessed against it, item by item: what it changes, what it contradicts, what is new and what it removes — each with the exact quote and a proposal. You decide; accepted items are applied by Sync.
Every use case specification carries its screens, component by component. Deus draws them as lo-fi wireframes, so the screens can be reviewed with the client before anything is built.
Arrange the whole specification as one document — modules in BABOK order, specifications by use case, the traceability matrix and the change log — and export it for your team or for the agent that writes the code.
Talk to the project. Ask about the documents or the specification, ask how the project stands, or tell Deus what to build. Anything that costs credits waits for your confirmation.
The whole BABOK v3 guide as one sphere inside the app: knowledge areas, tasks, inputs and outputs, techniques, guidelines and stakeholders, with every connection between them — and which techniques Deus covers.
Every item has a stable id and points to the one above it. Ask why a screen exists and the chain answers: this use case, for this requirement, for this stakeholder, for this goal. Business rules, data and acceptance criteria hang off the specification the same way.
Nothing is orphaned without you knowing. Deus checks the chain itself — no AI involved — and shows every gap and every reference to an id that does not exist.
Every one of these tools starts from a specification. None of them starts from the forest. Deus is where the specification comes from.
From interviews and documents to a BABOK-structured specification with traceability — without weeks of formatting.
One source of truth for scope. See what a change touches before you agree to it.
Use cases, business rules, data model and interfaces as a specification people and coding agents can build from.
Turn a tender into a structured scope, with every assumption traceable back to the document it came from.
Pilots, partnerships, a question or feedback — write to us directly. Both of us read what you send.