Ragnarock
Ragnarock AI

Giving the AI context

The four sources Ragnarock draws on — your SRS, documents, skills, and linked repositories — and how to strengthen each.

Ragnarock answers from your project's context. The richer that context, the better its answers and generated artifacts. There are four sources you control directly.

1. Your SRS

The Software Requirements Specification is the most important grounding material. Ragnarock and its specialized assistants quote and reason from it constantly:

  • The Developer Advisor grounds architecture and design answers in your SRS, referencing specific features, requirements, and constraints — and flags when something isn't covered.
  • The planner turns SRS features into tasks.
  • The QA assistant turns SRS features into test cases.

Build it through a guided conversation — see Building your SRS — and keep it accurate as scope changes.

2. Project documents

Documents in your Documentation workspace become part of the project picture the AI can summarize and reason about. Keeping them current means answers about "what we decided" or "how this should work" stay accurate. See Documentation.

3. Skills

Skills are short, reusable Markdown notes that steer the AI with your team's conventions — coding standards, review checklists, a domain glossary, naming rules, and the like. They keep the AI consistent across conversations without you repeating yourself.

Manage skills from the Skills area of your project.

Open Skills and choose New skill.
Give it a clear title, an optional summary, and write the guidance as Markdown.
Save it. Members can edit skills; owners and admins can delete them.

You can also export any skill as a .md or .txt file (with front matter) to reuse in tools like Cursor or Claude.

Tips for effective skills

  • Keep each skill focused on one concern.
  • Write imperative, checkable rules — "Always cite the requirement ID", not "try to reference requirements".
  • Update skills when conventions change so the AI never works from stale rules.

4. Linked repositories

Linking GitHub repositories lets implementation-focused answers reason about your real code structure rather than guessing. Connect GitHub on your account, then link repositories to the project. See GitHub & repositories.

Putting it together

For the strongest results, give Ragnarock all four: a complete SRS, current documents, a handful of focused skills, and your linked repositories. Then ask specific questions and pick the persona that matches your goal.

On this page