Extract modules, features, validations, domain services, events, subscribers, workflow states, and generate JSON from Business Requirements Documents (BRDs).
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 MarkdownGenerate FlexBase JSON import files from this BRDExtract domain services with full attributes and relationships from this BRDExtract workflow states for all entities that have status columnsThe 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
The extraction prompts are organized into dedicated files:
Markdown extraction (modules, features, events, domain services)
JSON generation (quick, complete, focused modules/services)
Legacy Migration: Legacy Migration → Markdown | Legacy Migration → JSON
New Application: New Application → Markdown | New Application → JSON
After extraction: Implementation Completion
Last updated