Analyse these business requirements: [REQUIREMENTS]. Identify the main objectives, actors, expected outcomes, dependencies and areas that need clarification.

Review these requirements and identify ambiguous, vague or potentially conflicting statements: [REQUIREMENTS]. Explain why each item may require clarification.

Generate a structured list of clarifying questions for these requirements: [REQUIREMENTS]. Group the questions by business goal, user, process, data, rules and exceptions.

Review this project description: [DESCRIPTION]. Identify potentially missing requirements and explain what additional information would be needed to validate them.

Help prioritise these requirements using business value, urgency, dependency, risk and implementation considerations: [REQUIREMENTS]. Explain the reasoning without inventing project constraints.

Compare these two requirements: [REQUIREMENT A] [REQUIREMENT B] Identify similarities, differences, conflicts and questions that need stakeholder confirmation.

Create a requirements-quality checklist for [PROJECT TYPE]. Include clarity, completeness, testability, traceability, business value, dependencies and acceptance conditions.

Classify these requirements as business, functional, non-functional or other. Explain each classification: [REQUIREMENTS]. Flag anything that cannot be confidently classified.

Analyse these requirements and identify possible dependencies between them: [REQUIREMENTS]. Present the relationships clearly and distinguish confirmed dependencies from assumptions.

Create a requirements traceability structure linking business objectives to requirements, features, acceptance criteria and validation activities: [PROJECT DETAILS].

Based on this project description: [PROJECT], identify potential stakeholder groups and explain their likely interests, responsibilities and information needs.

Create a stakeholder analysis matrix for: [STAKEHOLDERS]. Consider influence, interest, impact, concerns and recommended engagement approach.

Create stakeholder interview questions for [STAKEHOLDER ROLE]. Focus on goals, problems, current processes, requirements, risks and desired outcomes.

Create a structured 45-minute stakeholder interview plan for [PROJECT]. Include introduction, discovery questions, follow-ups, validation and closing questions.

Analyse these stakeholder comments: [COMMENTS]. Group concerns into themes and identify which items may require follow-up or formal decisions.

Review these stakeholder requirements: [REQUIREMENTS]. Identify conflicting goals or expectations and suggest neutral questions that could help resolve them.

Create a stakeholder communication plan for [PROJECT]. Include audience, information needed, communication format, frequency, owner and escalation considerations.

Turn these project decisions into a structured decision log: [NOTES]. Include decision, date, rationale, decision-maker, impact and follow-up actions.

Turn this process description into a structured process flow: [PROCESS]. Identify actors, inputs, activities, decisions, outputs and exceptions.

Analyse this business process: [PROCESS]. Identify possible bottlenecks, delays, handoffs, duplication and unclear responsibilities. Separate observations from hypotheses.

Review this current process: [PROCESS]. Suggest improvement opportunities and explain the expected business benefit and possible trade-offs.

Compare the current-state process with this proposed future state: [CURRENT STATE] [FUTURE STATE] Highlight changes, benefits, risks and open questions.

Analyse this workflow and identify repetitive manual activities that may be candidates for simplification or automation: [WORKFLOW]. Do not assume automation is always appropriate.

Review this standard process: [PROCESS]. List realistic exception scenarios that should be considered during requirements analysis.

Extract and organise the business rules from these notes: [NOTES]. Identify conditions, actions, exceptions and unresolved rules.

Review this process and identify duplicated activities, repeated data entry, unnecessary approvals and redundant handoffs: [PROCESS].

Create discovery questions for understanding the end-to-end process of [BUSINESS PROCESS]. Cover actors, systems, inputs, outputs, rules, exceptions and pain points.

Convert these requirements into clear user stories: [REQUIREMENTS]. Use a consistent structure and preserve the original business intent.

Review this user story for clarity, user value, scope and testability: [USER STORY]. Suggest a revised version and explain the changes.

Create clear acceptance criteria for this user story: [USER STORY]. Cover the expected behaviour and important conditions without inventing requirements.

Review this feature: [FEATURE]. Identify possible edge cases, exception scenarios and unusual inputs that the team should consider.

This user story appears too large: [USER STORY]. Suggest smaller stories while preserving the overall business objective and logical delivery sequence.

Create a practical Definition of Done checklist for [PROJECT/FEATURE]. Include functional, quality, documentation and validation considerations.

Create user personas for this product: [PRODUCT]. For each persona include goals, tasks, frustrations, constraints and information needs.

Create a user journey for [USER] completing [TASK]. Include stages, actions, questions, pain points and desired outcomes.

Analyse these user stories and identify potential dependencies: [STORIES]. Explain which relationships are confirmed and which require team validation.

Turn these meeting notes into a structured summary: [NOTES]. Include decisions, requirements, action items, owners, deadlines and unresolved questions.

Create a Business Requirements Document outline for: [PROJECT]. Include objectives, scope, stakeholders, requirements, assumptions, constraints, risks and acceptance considerations.

Review this requirements document for clarity, consistency, structure and missing information: [DOCUMENT]. Suggest improvements without changing the intended business meaning.

Create a concise executive summary from this analysis: [ANALYSIS]. Focus on business problem, key findings, implications, decisions and recommended next steps.

Create a 60-minute requirements workshop agenda for [PROJECT]. Include objectives, discussion topics, activities, decisions and expected outputs.

Extract action items from these notes: [NOTES]. For each identify owner, deadline if stated, dependency and status. Do not invent missing information.

Create a business glossary from these project notes: [NOTES]. Identify important terms, acronyms and domain-specific language. Flag terms whose meaning is unclear.

Analyse this dataset: [DATA]. Identify important patterns, anomalies, missing values and questions that require further investigation. Do not invent results.

Suggest useful business metrics for [BUSINESS/PROCESS]. For each metric explain what it measures, why it matters and what decisions it could support.

Review this historical business data: [DATA]. Identify meaningful trends and possible explanations. Clearly separate observed patterns from hypotheses.

Compare these business options: [OPTION A] [OPTION B] [OPTION C] Evaluate benefits, risks, costs, dependencies and unanswered questions. Do not make unsupported assumptions.

Create a decision matrix for selecting between: [OPTIONS]. Use these criteria: [CRITERIA]. Show assumptions and explain how changing the weighting could change the result.

Review this proposed business change: [CHANGE]. Identify possible business, operational, user, data and implementation risks. Separate known facts from assumptions.

Act as my business analysis assistant. Project: [PROJECT] Business objective: [OBJECTIVE] Stakeholders: [STAKEHOLDERS] Current process: [PROCESS] Known requirements: [REQUIREMENTS] Help me analyse requirements, identify gaps, prepare questions, organise documentation, identify assumptions and structure stakeholder discussions. Do not invent requirements or project facts. Clearly distinguish confirmed information, assumptions and questions that need validation.