Generate BRD
Route: Open BRD Generation
Assignee: Business Analyst 📝
The BRD (Business Requirement Document) captures all business requirements for a feature from the business perspective. AIPD generates the BRD through a 3-step sequential flow: configure sources → answer criteria → receive the finalized document. Content is streamed in real time — text appears progressively instead of waiting for completion.
Interface overview
The screen is divided into two areas:
- Left column (Ticket Sidebar): List of BRD tickets in the project, with a search box and a create-new button.
- Right area (Main Panel): A 3-step workspace for the selected ticket.
Ticket status is shown as a colored badge:
| Status | Meaning |
|---|---|
CREATED | Ticket has just been created; analysis has not started |
DRAFTING | BRD is being drafted |
WAITING_REVIEW | A review request has been sent |
APPROVED | BRD has been approved |
REJECTED | BRD was rejected and must be revised |
Step 1: Create a BRD Ticket
Click the "+" button at the top of the left column to open the new-ticket modal.
| Field | Required | Notes |
|---|---|---|
| Jira Ticket ID | No | Links to the corresponding Jira ticket |
| Summary | Yes | Short title of the requirement |
| Description | Yes | Detailed description of the context |
| Type | Yes | Epic or Task |
| Due Date | Yes | Deadline |
| Assignee | Yes | Person in charge |
| Labels | No | Classification labels |
| Components | No | Related components |
Click "Create". The new ticket appears in the list with status CREATED.
Step 2: Source — Configure analysis sources
Select a ticket from the list. The "Source" tab opens by default.
Add the information sources so the AI has enough context to generate an accurate BRD:
| Source | Description |
|---|---|
| Jira Tickets | Related Jira tickets — the AI reads them to understand the original requirement |
| Confluence Pages | Reference documents from Confluence |
| Uploaded Files | Uploaded document files (BRD, TRD, or others) |
| System Features | Select the systems and features impacted by this requirement |
| High Level Requirement | A free-text field to provide additional context directly to the AI |
Once enough sources have been added, click "Analyse".
The system moves to the next step and shows "AI is processing data... / Please wait while AI generates results" during processing.
Step 3: Information Collection — Answer criteria
When analysis completes, the tab switches automatically to "Information Collection".
The AI generates a list of Criteria Questions — each one covers a business aspect that must be clarified before writing the BRD. Examples: scope of application, preconditions, exceptional cases, and so on.
For each question:
-
Read the question content and the accompanying hint.
-
Type your answer into the input box below.
-
Click "Verify" — the system checks the answer and updates the status:
- ✅ Pass — the answer provides enough information
- ❌ Fail — more detail is required
-
Answer each question in turn.
Once all questions Pass, the system automatically moves to the next step and begins generating the BRD.
For questions you have no information to answer, or that do not apply to this feature, click "Skip". Skipped questions do not affect BRD generation — the AI will ignore that criterion and continue with the remaining questions.
The more specific and complete your answers, the less editing the generated BRD will need. Instead of a short reply like "Yes", explain the context and specific conditions clearly.
Step 4: BRD — Read, edit, and save
The "BRD" tab streams content into the editor in real time — text appears progressively until complete.
Edit the content
Once streaming finishes:
- Click "Edit" (pencil icon) to enter edit mode.
- Edit in the rich text editor — it supports headings, bullet lists, tables, code blocks, and Markdown.
- Click "Save" (✓ icon) to save the changes.
Click "Cancel" to discard and return to the previous content.
Switch to BDD
The dropdown above the editor lets you switch view modes:
- BRD — Business Requirement Document (default)
- BDD — Behavior Driven Development format (Given/When/Then)
Send the BRD for Review
Once the BRD content is complete, click "Request Review" in the footer. The ticket status changes to WAITING_REVIEW.
The reviewer is notified and can:
- Click "Approve" → status changes to
APPROVED - Click "Reject" → status changes to
REJECTED; the BA must revise and resubmit
An approved BRD (APPROVED) is automatically added to the Knowledge Base. From that point on, the AI Agent can reference this BRD when generating the Implementation Plan and Test Cases for the same feature.