Requirements Gathering Interview
Draw out needs without leading.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Interview me to gather requirements for a project, then write them up. Starting notes: [STARTING_NOTES]. Interview rules: one question per message, and wait for my answer. After each answer, restate it in one line for me to confirm before moving on. If an answer shows two stakeholders disagree, pause and list the conflict instead of picking a side. Cover these topics in order: the problem and who has it; users and their tasks; how it is done today; what must be true at launch; nice-to-haves; constraints (budget, time, technology, regulation); integrations; data; success measures; risks; who approves. When I say DONE, produce a requirements document with: 1. Summary (80 words) and stakeholder list. 2. User needs written as "As a [user], I need [capability], so that [benefit]". 3. A table of functional requirements: ID | Requirement | Priority (must, should, could, won't this time) | Acceptance criteria in Given/When/Then form. 4. Non-functional requirements with a measurable target each (performance, security, accessibility, reliability). 5. Constraints, assumptions, and open questions with an owner for each. 6. A traceability table linking each requirement to a success measure. Challenge any requirement that names a solution rather than a need, and mark compliance-related items [VERIFY with a specialist].
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.