You are a senior business analyst. I'm working on [PROJECT NAME] for [STAKEHOLDER/CLIENT]. 
Interview me with 10 targeted questions to uncover business requirements I might be 
missing. Focus on [business process/user needs/technical constraints].

Convert these raw stakeholder notes into formal business requirements using the standard 
BR format (ID, description, priority, acceptance criteria):

[PASTE YOUR NOTES HERE]

Business domain: [DOMAIN]
Project: [PROJECT NAME]

I have these 5 high-level business needs for [PROJECT]. For each one, write 3 
measurable acceptance criteria a QA team can actually test:

1. [NEED 1]
2. [NEED 2]
3. [NEED 3]
4. [NEED 4]
5. [NEED 5]

Write a user story in the format "As a [role], I want [feature], so that [benefit]" 
for each of these business scenarios. Include acceptance criteria for each:

Scenarios:
[SCENARIO 1]
[SCENARIO 2]
[SCENARIO 3]

Target users: [USER TYPES]
System: [SYSTEM NAME]

Review these requirements for ambiguity, missing edge cases, and conflicts. 
Flag anything that will cause problems during development or testing:

[PASTE REQUIREMENTS HERE]

I need to perform a gap analysis for [BUSINESS PROCESS] at [COMPANY/DEPARTMENT]. 
Current state: [DESCRIBE AS-IS STATE]
Desired future state: [DESCRIBE TO-BE STATE]

Identify the gaps, prioritize them by business impact, and suggest remediation steps.

Create an AS-IS process map in text/outline format for this workflow. Then identify 
3 inefficiencies and propose a TO-BE version that eliminates them:

Process: [PROCESS NAME]
Steps as described by stakeholders: [PASTE DESCRIPTION]
Department: [DEPARTMENT]

I'm analyzing the gap between our current [SYSTEM/CAPABILITY] and industry best 
practice. Research [INDUSTRY] benchmarks for [METRIC/CAPABILITY] and show me 
where we likely fall short based on this context:

[CONTEXT ABOUT CURRENT STATE]

Conduct a SWOT analysis on our current [BUSINESS PROCESS OR SYSTEM] based on 
these stakeholder inputs. Be specific — no generic statements:

Stakeholder feedback: [PASTE INPUTS]
Process/system: [NAME]
Company size/industry: [CONTEXT]

List every assumption embedded in this business case or requirements document 
and flag which ones represent the highest risk if proven wrong:

[PASTE DOCUMENT]

Write an executive summary (max 300 words) of this business requirements document. 
Emphasize business value, timeline impact, and top 3 risks. Audience: [C-SUITE/VP-LEVEL]:

[PASTE BRD OR SUMMARY]

I need to communicate a scope change to [STAKEHOLDER NAME/ROLE]. The change is: 
[DESCRIBE CHANGE]. Impact: [TIMELINE/COST/RESOURCES AFFECTED]. 

Write a professional email that explains the change clearly, owns the impact, 
and proposes next steps. Tone: [DIRECT/DIPLOMATIC/URGENT].

Create a status report for [PROJECT NAME] — week of [DATE]. Format it for 
[EXECUTIVE/PROJECT SPONSOR] consumption with these sections: 
- Accomplishments this week
- Next week priorities
- Risks and blockers
- Decisions needed

Raw updates: [PASTE YOUR NOTES]

Prepare talking points for a 15-minute stakeholder presentation on [TOPIC/PROJECT]. 
Audience: [WHO WILL BE IN THE ROOM]. Key message I need to land: [CORE MESSAGE]. 
Anticipated objections: [LIST THEM].

Rewrite this requirements section so a non-technical stakeholder in [INDUSTRY] 
can approve it without asking 10 clarifying questions:

[PASTE SECTION]

Build a decision matrix to evaluate [NUMBER] vendor options against these criteria. 
Weight each criterion and score the options based on this information:

Criteria and weights: [LIST CRITERIA AND IMPORTANCE]
Vendor options: [VENDOR A], [VENDOR B], [VENDOR C]
Information about each: [PASTE WHAT YOU KNOW]

I have this dataset/summary from [SYSTEM/REPORT]. Identify the top 3 insights 
relevant to [BUSINESS DECISION] and quantify the impact where possible:

Data: [PASTE DATA OR SUMMARY]
Decision context: [WHAT ARE WE DECIDING]

Create a cost-benefit analysis framework for [PROPOSED INITIATIVE]. 
Include tangible costs, intangible costs, direct benefits, and indirect benefits. 
Use a 12-month horizon. Budget context: [ROUGH BUDGET RANGE].

I need to validate whether [HYPOTHESIS ABOUT BUSINESS PROBLEM] is correct. 
What data should I collect, who should I interview, and what would disprove 
this hypothesis? Context: [BRIEF SITUATION DESCRIPTION].

Summarize the key findings from this business process analysis and format them 
as board-ready bullet points with supporting evidence:

Analysis: [PASTE CONTENT]
Audience: [BOARD/LEADERSHIP TEAM]

Write a full use case document for [FEATURE/FUNCTION] including:
- Use case ID and name
- Actors (primary and secondary)
- Preconditions
- Main success scenario (step-by-step)
- Alternative flows
- Exception flows
- Postconditions

System: [SYSTEM NAME]
Business context: [BRIEF DESCRIPTION]

Generate 10 edge cases for this user story that a QA team should test but 
probably hasn't thought of:

User story: [PASTE USER STORY]
System: [SYSTEM]
User type: [WHO IS PERFORMING THE ACTION]

Convert this business requirement into a test scenario table with columns: 
Test ID, Description, Input, Expected Output, Pass/Fail criteria:

Requirement: [PASTE REQUIREMENT]
System behavior: [DESCRIBE HOW SYSTEM SHOULD WORK]

I need UAT scripts for [FEATURE]. Write 5 test scripts in plain language 
that a non-technical business user can execute to validate the feature works 
as expected:

Feature description: [DESCRIPTION]
Acceptance criteria: [LIST THEM]

Review this use case and identify missing alternative flows, system failures, 
and boundary conditions that should be documented before development starts:

[PASTE USE CASE]

Perform a change impact assessment for [PROPOSED CHANGE] at [ORGANIZATION/DEPARTMENT]. 
Analyze impact across: people, process, technology, and data. 
Rate each impact as High/Medium/Low and identify change management actions needed.

Proposed change: [DESCRIPTION]
Affected departments: [LIST]
Timeline: [TIMELINE]

Write a stakeholder impact matrix for [PROJECT] with columns: 
Stakeholder, Role, Impact Level, Interest Level, Current Sentiment, 
Recommended Engagement Strategy.

Stakeholders I've identified: [LIST THEM]
Project description: [BRIEF DESCRIPTION]

I need to build a business case for [INITIATIVE]. Audience is [DECISION MAKER]. 
Write a structured business case covering: problem statement, proposed solution, 
alternatives considered, financial impact, risks, and recommendation.

Context: [PASTE RELEVANT CONTEXT]
Budget sensitivity: [LOW/MEDIUM/HIGH]

Draft a transition plan outline from [CURRENT STATE] to [FUTURE STATE] for 
[BUSINESS UNIT/SYSTEM]. Include key milestones, dependency mapping, and 
risk mitigation for the top 3 transition risks.

What change resistance should I anticipate when rolling out [CHANGE] to 
[TEAM/DEPARTMENT]? For each resistance type, suggest a specific mitigation tactic.

Organizational culture: [DESCRIBE BRIEFLY]
Change description: [WHAT IS CHANGING]
Past change history: [ANY RELEVANT CONTEXT]

Design a 2-hour requirements workshop agenda for [PROJECT] with [NUMBER] stakeholders 
from [DEPARTMENTS]. Include: ice-breaker, structured elicitation activities, 
conflict resolution time, and output deliverables.

Workshop goal: [WHAT YOU NEED TO LEAVE WITH]
Known tensions: [ANY CONFLICTS AMONG STAKEHOLDERS]

Create a requirements traceability matrix template for [PROJECT TYPE]. 
Include columns that trace from business objective → requirement → 
design decision → test case → business outcome.

Write 15 discovery interview questions for a [ROLE TYPE] stakeholder on 
[PROJECT/PROCESS]. Mix open-ended exploration with specific probes to surface 
pain points they won't volunteer.

Project context: [BRIEF DESCRIPTION]
What I already know: [CONTEXT]
What I'm trying to find out: [OBJECTIVES]

Facilitate a virtual brainstorm on [PROBLEM STATEMENT]. Give me: a warm-up prompt, 
3 structured ideation rounds with different thinking constraints, and a 
prioritization method I can run in 10 minutes.

Create a meeting summary template for [TYPE OF MEETING — requirements review, 
design walkthrough, sprint planning] that captures: decisions made, open items, 
action owners, and follow-up deadlines. Make it scannable in under 90 seconds.