Prompt Library

Based on the following process description, generate a complete BRD with sections: Overview, Business Context, Functional Requirements (FR-XXX format), Acceptance Criteria, Data Inputs/Outputs, Process Flow, and Regulatory References. Process: [DESCRIBE PROCESS]

Add OVD (Officially Valid Document) acceptance rules per RBI Master Direction on KYC (2016, updated Feb 2023). Include: list of accepted OVDs, validation rules for each, exception handling for name mismatches, and regulatory references.

Define the exception handling flow when a name mismatch is found in the CKYC registry. Include: mismatch threshold percentages, escalation paths, manual review process, audit trail requirements, and customer communication templates.

List all components downstream of [COMPONENT] that consume the [DATA_ELEMENT]. For each component, specify: dependency type (direct/indirect), data consumed, impact if data changes, and owner.

Generate a User Story in the format: As a [ROLE], I want to [ACTION], So that [BENEFIT]. Include 5-7 acceptance criteria in Given-When-Then format, story points estimate (Fibonacci), priority (High/Medium/Low), and technical notes.

/diagram Generate a Mermaid sequence diagram showing the interaction between [SYSTEM_A] and [SYSTEM_B] for the [PROCESS] flow. Include: actors, API calls with method and endpoint, response codes, error paths, and timing annotations.

/diagram Generate a Mermaid ER diagram for the [MODULE] data model. Include all entities, attributes (with data types), primary keys, foreign keys, and relationships (one-to-many, many-to-many).

Convert the following process description into a structured SOP with 6 mandatory sections: 1. Purpose, 2. Scope, 3. Roles & Responsibilities, 4. Procedure Steps (numbered), 5. Exceptions, 6. References. Process: [DESCRIBE PROCESS]

/research Embedded Lending in India 2025: Provide market size, top 5 competitors, 3 emerging trends, regulatory landscape, and 8 credible sources.

/test-cases-suggest Generate comprehensive test cases for [MODULE] based on the BRD. Include: happy path tests, negative tests, edge cases, performance tests, and security tests. Format as a table with TC-ID, Description, Preconditions, Steps, Expected Result.

/critique Review this BRD for: missing mandatory sections, vague acceptance criteria, untestable requirements, missing regulatory references, data model gaps, and integration points not covered. Provide a completeness score and specific recommendations.

/explain Explain the following RBI regulatory requirement in plain language, its impact on the [PRODUCT/MODULE], and what functional requirements it generates: [REGULATORY_REFERENCE]

Raise a Change Request against [BRD_TITLE]. Change type: [Addition/Modification/Deletion]. Section affected: [SECTION]. Reason for change: [REASON]. Proposed change: [CHANGE]. Regulatory basis (if any): [REGULATION].

Generate a complete Understanding Document for [COMPONENT/SYSTEM] with all 6 mandatory sections: 1. Overview, 2. Functional Specification, 3. Technical Specification, 4. Data Model (with JSON schema), 5. Integration Points (with API specs), 6. Edge Cases.

Review this BRD and identify regulatory gaps. Check against: RBI Master Directions, PMLA Rules, IT Act 2000, DPDP Act 2023, and any product-specific regulations. List each gap with: regulation reference, requirement, current coverage, and recommended addition.

Generate a technical integration specification for [API_NAME]. Include: base URL, authentication method, key endpoints (method, path, request/response schema), error codes, rate limits, SLA, and retry strategy.

/research AI-powered underwriting in BFSI 2025: Market size, key vendors (Zest AI, Scienaptic, etc.), adoption rates, regulatory considerations in India, and 5 case studies.

/test-cases-suggest Generate edge case test scenarios for [MODULE] focusing on: boundary conditions, null/empty inputs, concurrent requests, timeout scenarios, and data integrity checks.

/diagram Generate a Mermaid flowchart for the [PROCESS] showing: start/end nodes, decision points, process steps, error paths, and system boundaries.

Summarize the [COMPONENT] BRD for a non-technical stakeholder presentation. Include: business objective (1 sentence), key features (5 bullets), business benefits, risks, and timeline. Keep it under 200 words.

Convert the following Functional Requirements into testable Acceptance Criteria in Given-When-Then format. Each FR should have at least 2 ACs. FRs: [LIST_FRs]

/critique Review this Understanding Document for technical completeness. Check: data model has all entities, integration points have API specs, edge cases cover failure scenarios, and technical spec has deployment/infrastructure details.

/test-cases-suggest Generate a regression test suite for [MODULE] after the change [CHANGE_DESCRIPTION]. Focus on: impacted functionality, integration points, and previously reported defects.

/research KYC technology vendors in India 2025: Market overview, top vendors (IDfy, Signzy, KARZA, etc.), feature comparison, pricing models, RBI compliance status, and integration complexity.

Extract all exception flows from the [BRD_TITLE] and convert them into a structured SOP. For each exception: define trigger condition, responsible role, step-by-step resolution process, escalation path, and SLA.

/research Consent architecture frameworks for financial data sharing in India 2025: Account Aggregator framework, DPDP Act 2023 requirements, consent manager landscape, and implementation best practices.