Generate FRD / Implementation Plan
Route: Open Implementation Plan
Assignee: Developer | Solution Architect 🔧
The Implementation Plan is a detailed technical document that describes how to implement a feature from the technical perspective. Unlike the BRD, which focuses on business requirements, the Implementation Plan goes into the technical detail a Developer needs to start implementing right away.
The flow has 5 sequential steps: configure sources → FRD criteria → FRD editor → Specification criteria → Specification Document.
Interface overview
- Left column: List of Implementation Plan tickets with status badges and a search box.
- Right area: A 5-step workspace for the selected ticket.
Ticket status values are the same as for BRD: CREATED → DRAFTING → WAITING_REVIEW → APPROVED / REJECTED.
Step 0: Create a ticket
Click "+" in the left column → fill in the fields as you would for a BRD (Summary, Description, Type, Due Date, Assignee, Labels, Components) → click "Create".
Step 1: Source — Configure analysis sources
The "Source" tab opens by default. Add information sources for the AI:
| Source | Description |
|---|---|
| BRD Selections | Select an approved BRD — the primary source for generating the Implementation Plan |
| Jira Tickets | Related Jira tickets |
| Confluence Pages | Reference documents |
| Uploaded Files | Uploaded document files (BRD, TRD, or others) |
| System Features | Impacted systems and features |
| Description | Additional context |
Always select an approved BRD into BRD Selections before analysing. An Implementation Plan generated from a BRD keeps the technical requirements consistent with the business requirements.
Click "Analyse" to begin. The system shows "AI is processing data..." while working.
Step 2: Information Collection — FRD criteria
The "Information Collection" tab shows a list of FRD Criteria Questions generated by the AI — focused on technical aspects such as: data types, business logic constraints, edge cases, integration points, etc.
For each question:
- Read the question and the accompanying hint.
- Type your answer into the input box.
- Click "Verify" — the system validates and shows ✅ Pass or ❌ Fail.
- Complete every question until all of them Pass.
The system advances automatically once the conditions are met.
Step 3: FRD — Functional Requirement Document
The "FRD" tab shows the Functional Requirement Document streamed into the editor.
- Click "Edit" to edit the content in the rich text editor.
- Click "Save" to save.
This section describes the functional requirements at the business-technical level, before going into implementation detail for each component.
After reviewing and saving the FRD, click "Analyse" to start the Specification criteria analysis step. The system moves to the next step and shows "AI is processing data..." while working.
Step 4: Information Collection — Specification criteria
A second "Information Collection" step appears with a deeper set of questions — focused on technical details for each type of work item (API, DB, Queue, UI).
Proceed as in step 2: answer → Verify each question → the system advances automatically.
Step 5: Specs — Specification Document
The "Specs" tab shows the Specification Document — a detailed technical document consolidated from the entire preceding analysis.
The content is streamed into the editor in real time — text appears progressively while the AI generates it. During streaming, the editor shows "AI is processing data...".
After streaming finishes:
- Click "Edit" to enter edit mode.
- Edit the content in the rich text editor — it supports headings, bullet lists, tables, code blocks, and Markdown.
- Click "Save" to save the changes.
Send for Review
- Click "Request Review" when the Specification Document is complete → the status changes to
WAITING_REVIEW. - The reviewer clicks "Approve" or "Reject".
- After approval, the Implementation Plan can be referenced by the QA Engineer when generating Test Cases.
If the Specs tab is empty, check whether both rounds of Information Collection were completed. Step 2 (FRD criteria) and step 4 (Specification criteria) must both Pass before the Specification Document is generated.