The same spec that drives the diagrams, rendered as a formatted document you can hand to a client.
Switch to the Spec document view and kratai renders your Use Case Model, Data Model, and NFRs as a formatted Software Requirements Specification — the same underlying data as the diagrams, laid out as a document a non-technical reader can follow without implementation detail getting in the way.
Use the Download SRS (PDF) button in the document view to export it. The PDF keeps the same section structure as the on-screen document, with pagination rules that keep headings and entity blocks from getting orphaned across a page break.
Every generated SRS includes:
UC-1, UC-2, ...), with its goal, preconditions, main flow, postconditions, and any use-case-scoped NFRs.The SRS covers what the system does and the data it works with — the Class Diagram covers how the code is actually structured. See Generate a Class Diagram for how it's generated and what it's useful for.