Requirements

Fast code is useless without clear direction. The Requirements module gives teams a collaborative, agent-assisted workspace to define, debate, and refine requirements.

Requirements documents define what the product should do and why, without prescribing how it is built. They capture business context, user needs, feature behavior, and technical constraints in a human-readable form.

Requirements are organized into two categories:

• Product Overview Documents provide high-level strategic context shared across the team.
• Feature Requirements Documents define individual product capabilities in a clear, testable way. Each document represents one feature and acts as its authoritative specification. Feature Requirements align with Feature Blueprints so product and technical intent stay in sync.

Getting started

Step 1: Initialize requirements

When a project is created, Product Overview and Technical Requirements documents are generated with placeholder content. Feature Requirements are created explicitly based on user intent.

A Getting Started alert guides you to either:

• Reverse-engineer requirements from artifacts and code.
• Create new requirements from scratch.

Step 2: Define product context

If you are starting a new product, the agent guides you through a structured Q&A covering:

• The business problem
• The current solution
• The desired outcome
• Target users

The agent drafts the initial overview documents and proposes an initial feature set.

Step 3: Create Feature Requirements

After the product's high-level purpose is established, collaborate with the agent to define the initial Feature Requirements Documents. Each document starts with a standard Markdown outline. Customize that outline from Overview → Settings → Requirements.

Collaboration and versioning

The document editor supports shared editing, comments, and mentions. All documents are versioned automatically, allowing you to:

• View document history
• Compare versions
• Compare aggregate versions across the entire project

Requirements Agent

The Requirements Agent assists throughout the requirements lifecycle.

Drafting and initialization

The agent can analyze notes, transcripts, designs, images, codebases, and other artifacts to draft structured requirements and propose features.

Review and quality checks

The agent reviews documents for ambiguity, gaps, conflicts, and duplication. It surfaces issues as flagged comments and summarizes them in the agent panel.

Question answering

Ask targeted questions to receive concise answers with direct references to source content.

Feature organization

The agent can suggest creating, splitting, merging, or reorganizing features. All structural changes require user confirmation.

Alignment with Blueprints

The agent monitors drift between Feature Requirements and Blueprints and guides you through resolution workflows when discrepancies arise.

Import and export

Individual documents

Import .docx or .md files into a document to create a new version. Export documents to .pdf, .docx, or .md.

Aggregate export

Export all requirements as one concatenated file from the aggregate view, preserving their order and embedded images.

Best practices

• Treat requirements as living documents.
• Anchor strategy in Product Overview Documents.
• Keep Feature Requirements precise and implementation-agnostic.
• Use the agent early, then refine collaboratively.
• Sync regularly with Blueprints to avoid drift.

Ready to translate requirements into technical specifications? Learn about Blueprints.