Building your SRS
Create a complete Software Requirements Specification through a guided AI conversation.
The Software Requirements Specification (SRS) is the foundation of a Ragnarock project. It captures what you're building — features, functional and non-functional requirements, user stories, and scope — in a structured form. A completed SRS unlocks task plans, architecture documents, features, and test cases, and it grounds every AI answer.
Start a requirements session
/srs and choose Start SRS session — or simply start describing what you want to build in your own words.Watch it build live
As you answer, the SRS preview in the right-hand panel fills in. You can follow progress two ways in the panel:
- Sections view — requirements grouped by area (overview, user roles, functional requirements, user stories, non-functional requirements), with a progress bar per section.
- Document view — the SRS rendered as a readable document. Use the expand control to open it full-screen.
A progress indicator climbs toward 100% as more of the specification is captured.
Complete the SRS
Keep answering until the specification is complete. A finished SRS:
- Marks the requirements at 100% / Done.
- Unlocks the
/planand/doccommands in Ragnarock. - Enables Generate Plan, Generate Test Suite, and the Features list.
- Appears as an SRS card in your Documentation workspace, where you can preview or download it.
You don't have to finish in one sitting. Ragnarock keeps your draft, so you can return later and continue the conversation where you left off.
Refine an existing SRS
If an SRS already exists, running /srs again lets you revisit and refine it — the AI summarizes
what's there and asks what you'd like to change. Update the SRS whenever scope shifts so that plans,
docs, and tests generated afterward reflect reality.
What the SRS captures
A complete SRS typically includes:
- Features — the product's capabilities, which the AI also extracts into the Features list.
- Functional requirements — what the system must do.
- Non-functional requirements — performance, security, and other quality attributes.
- User stories — role / goal / benefit statements.
- Acceptance criteria and scope — what "done" looks like and what's explicitly out of scope.