# BRD Extraction Prompts - md file

> Extract modules, features, validations, domain services, events, subscribers, workflow states, and generate JSON from Business Requirements Documents (BRDs).

## How to Use

Tell your AI agent what you need. It will load the extraction conventions and rules automatically from the MCP server.

**Example prompts you can give your AI agent:**

```
Analyze this BRD and extract all modules and features to Markdown
```

```
Generate FlexBase JSON import files from this BRD
```

```
Extract domain services with full attributes and relationships from this BRD
```

```
Extract workflow states for all entities that have status columns
```

***

## Key Rules (Applied Automatically)

The agent loads complete extraction conventions via MCP tools. These are the most important rules to be aware of:

* **Module names must be PLURAL** PascalCase (e.g., `Orders`, `Customers`, `Payments`)
* **All names must be PascalCase** — modules, features, validations, events, subscribers, domain services
* **Every operation = one feature** — `CreateUser`, `UpdateUser`, `GetUserById` are 3 separate features
* **Valid operation types:** CREATE, UPDATE, DELETE, SOFTDELETE, GETPAGEDLIST, GETLIST, GETBYID, GETSINGLE (READ is NOT valid)
* **featureType:** WebAPI (user-initiated) or CronJob (scheduled)
* **isEventual:** `false` for GET operations, `true` for mutating operations (unless time-sensitive like financial deductions)
* **Events** must include conditions: `OnSuccess` (primary) or `OnFailed` (primary)
* **Only complex validations** in JSON — skip simple attribute validations (Required, MaxLength, email format)
* **Large files are split automatically** — per-module Markdown and JSON files

***

## Prompts

The extraction prompts are organized into dedicated files:

| File                                                                                    | Contents                                                         |
| --------------------------------------------------------------------------------------- | ---------------------------------------------------------------- |
| [BRD Extraction → Markdown](/flexbase-mcp-ai-prompts/brd-extraction-prompts-md-file.md) | Markdown extraction (modules, features, events, domain services) |
| [BRD Extraction → JSON](/flexbase-mcp-ai-prompts/brd-extraction-prompts-json-file.md)   | JSON generation (quick, complete, focused modules/services)      |

***

## Related

* **Legacy Migration:** [Legacy Migration → Markdown](/flexbase-mcp-ai-prompts/legacy-migration-prompts-md-file.md) | [Legacy Migration → JSON](/flexbase-mcp-ai-prompts/legacy-migration-prompts-json-file.md)
* **New Application:** [New Application → Markdown](/flexbase-mcp-ai-prompts/new-application-add-moduels-features-to-existing-application-prompts-md-file.md) | [New Application → JSON](/flexbase-mcp-ai-prompts/new-application-add-moduels-features-to-existing-application-prompts-json-file.md)
* **After extraction:** [Implementation Completion](/flexbase-mcp-ai-prompts/implementation-completion-prompts.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.flexbase.in/flexbase-mcp-ai-prompts/brd-extraction-prompts-md-file.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.