Document requirements and process flows
Gathers and structures business requirements, process flows, and acceptance criteria.
The prompt
Role: Act as a business analyst documenting requirements and process for a change.
Context: The change / initiative and its objective: [OBJECTIVE]. Stakeholder inputs / interview notes: [INPUTS]. The current process as described: [AS_IS]. Pain points and their impact: [PAIN_POINTS]. Systems involved: [SYSTEMS]. Constraints and compliance needs: [CONSTRAINTS]. Definition of done for this analysis: [DOD].
Task: Produce: (1) functional requirements (each: ID, statement, rationale, priority, acceptance idea), non-functional requirements, and data requirements; (2) an as-is process flow (steps, actors, systems, handoffs, decision points, pain points marked); (3) a to-be process flow addressing the pain points; (4) the gap analysis (what must change: process, system, data, role); (5) open questions and assumptions.
Format: Sections: Requirements (tables) | As-is flow (numbered) | To-be flow (numbered) | Gap analysis | Open questions & assumptions. ~600 words.
Verification: Every requirement must trace to an input or an objective; flag requirements that are solution choices without a stated need. Mark process steps that are assumed.
Validation: Walk the to-be flow with a stakeholder who does the work today: is it actually workable, or does it move the pain elsewhere? Adjust.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Projects & Operations prompts
What to fill in
- OBJECTIVE
- INPUTS
- AS_IS
- PAIN_POINTS
- SYSTEMS
- CONSTRAINTS
- DOD
How this prompt is built
This prompt follows the RCTFVV structure (Role, Context, Task, Format, Verification, Validation). RCTFVV extends RCTF with two checking steps. Verification asks the model to review its own draft against your requirements; Validation asks it to flag assumptions and gaps you should confirm.
Related prompts
- Design project stage gates with clear entry and exit criteriaA lightweight phase-gate framework with evidence-based criteria, decision options, and governance that fits your project sizes.
- Build a RAID log (risks, assumptions, issues, dependencies)Captures and tracks the risks, assumptions, issues, and dependencies on a project.
- Create a risk register with mitigationsIdentifies, scores, and plans responses to project or business risks.
- Assess the impact of a change requestEvaluates a scope change's impact on time, cost, quality, and risk.