Ragnarock
Getting Started

Your first project

A guided walkthrough from creating a project to a generated task plan, in about ten minutes.

This walkthrough takes you through the core Ragnarock loop end to end. By the end you'll have a project with a complete SRS, a generated task plan, and supporting documents — all created with the AI.

Before you start

Make sure you've created your account and are inside an organization.

1. Create a project

Open Projects and choose New project.
Give it a name and a short description, then create it. The project is created inside your active organization.
Open the project to land on its Overview.

2. Set your persona

Open Members, find yourself, and confirm your personas match how you'll work — for example Developer if you'll ask implementation questions, or Business owner if you're focused on scope. Personas shape how the AI responds. See Members & roles.

3. Build your requirements with Ragnarock

Open Ragnarock — this is your project's AI assistant.

Type /srs and select Start SRS session, or just describe your idea in your own words.
Answer the AI's questions about your project — who it's for, what it must do, and any constraints.
Watch the SRS preview build up in the panel on the right as you talk. A progress indicator climbs toward 100%.
Keep going until the SRS is complete. A completed SRS unlocks plans, documents, features, and test cases.

For the full details see Building your SRS.

4. Generate a task plan

Once the SRS is complete, type /plan in Ragnarock (or use Generate Plan on the Tasks board). The AI breaks your requirements into tasks organized by delivery phase. Open Tasks to see them appear, then drag cards between columns as work progresses. See Generate a task plan.

5. Generate supporting documents

Still in Ragnarock, type /doc sad to generate a Software Architecture Document from your SRS (or hld, lld, adr for other types). The result appears in the right panel and is saved to Documentation. See Architecture documents.

6. Generate test cases

Open Test Cases and choose Generate Test Suite. The QA assistant reads your SRS and drafts test cases for each feature. See Test cases.

7. Bring in your team and code

  • Invite teammates on Members and set their roles and personas.
  • Link your GitHub repositories under Repositories so the AI can reason about real code.
  • Connect a coding agent over MCP so tools like Claude Code and Cursor work with full project context.

What you've built

You now have a connected project: requirements, a plan, documents, and tests that all trace back to the same source of truth. From here, explore each area in depth:

On this page