Skip to Content
Getting StartedFor Product Managers

Getting Started for Product Managers

Dot•requirements helps you write better requirements, faster. The AI assistant catches edge cases you might miss, ensures consistency across your team, and gives you a single source of truth that developers reference in their tests.

What You’ll Get

  • AI that improves your product documentation — Brainstorming, identifying key context, catching ambiguity, and ensuring testable clarity
  • Guard rails for consistency — A paved road for writing requirements as a team, so everyone doesn’t reinvent the wheel
  • Find problems early — Correcting confusion during specification is cheaper than fixing bugs in production
  • A single source of truth — No more sync pain across issue trackers, documentation tools, and chat. Requirements live in one place and are visible anywhere.
  • Automatic coverage visibility — See which requirements are being tested without asking

Get Started

1. Log in

Head to app.dotrequirements.io  and sign in with your Google or GitHub account.

2. Create a team and project

After logging in, create a team (this is your organization) and then create a project. Projects contain your requirements documents, and generally correspond to a single product or codebase.

3. Create your first document

Click New Document to open the composer. Give it a title that describes what you’re specifying — “Login Flow”, “Checkout Process”, “User Profile”.

Write Requirements with the AI Assistant

The AI assistant appears in the right sidebar of every document. Use it to draft requirements, review what you’ve written, and suggest additions or improvements.

Draft requirements from a conversation

Tell the assistant what you’re trying to specify:

“Help me write requirements for a login page with email and password authentication”

The assistant asks clarifying questions, suggests edge cases to consider, and drafts properly structured requirements.

Review for clarity and completeness

Ask the assistant to review what you’ve written:

“Review this document for clarity and style”

It will look for things like:

  • Ambiguous language — “the system should respond quickly” → how quickly?
  • Missing edge cases — what happens when the password is expired?
  • Untestable statements — requirements that can’t be objectively verified
  • Inconsistent terminology — using “user” and “customer” interchangeably

These are the kinds of issues that often slip through until someone tries to implement or test the requirement.

Create requirements manually

You can also write requirements yourself:

  1. Type /requirement to insert a new requirement block
  2. The block gets an auto-generated ID (like REQ-1)
  3. Write a clear, testable statement of expected behavior
  4. Add child criteria to elaborate on complex requirements

Note: dot•requirements is framework agnostic, but if your team uses a specific format like Gherkin, requirements support labels (including Given/When/Then) out of the box.

Share with Your Team

Your requirements live in one place, but they are accessible to team members where they do their work.

Invite team members

  1. Go to Team Settings (click your team name in the sidebar)
  2. Click Invite Member
  3. Generate an invite link and share it via email or Slack

Anyone who accepts the invite joins your team and can see all project requirements.

Developers pull requirements into their codebase

Developers on your team run a command:

dotreq pull

This downloads your requirements as Markdown files. They reference these requirements directly in their test descriptions, so the requirement text appears in test output. When you update requirements, they pull again to get the latest.

Track Coverage

The Coverage page shows which requirements have tests.

What you’ll see

  • Requirement hierarchy with coverage ratios (e.g., “4/5 tested”)
  • Status badges — tested (green), untested (gray), partial (yellow)
  • Test file references — which test covers each requirement
  • Branch filtering — see coverage on specific branches (useful around releases)

Coverage updates automatically as developers write and run tests, so you can check the status without asking.

Next Steps

  • Start earlier with Discovery Boards — Use Discovery for brainstorming before you’re ready to write formal requirements
  • Sync to Jira and Confluence — See Atlassian Add-ons to view requirements alongside your issues and pages
  • Already using an AI assistant? — If you use Claude Code or Cursor, you can compose requirements directly from your assistant. See Getting Started for AI-First Builders
Last updated on
For DevelopersFor AI-First Builders