Confluence Product Requirements Page From a Brief
Structure a brief into a requirements page with open questions.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Convert this brief into a Confluence product requirements page. Brief: [BRIEF]. Product and users: [PRODUCT_AND_USERS]. Goal and success measures: [GOALS]. Stakeholders: [STAKEHOLDERS]. Release target: [RELEASE_TARGET]. Use the sections Background; Problem statement; Goals and non-goals; Users and scenarios; Requirements as a numbered table with Priority (must, should, could), Acceptance condition and Source; Non-functional requirements; Dependencies; Assumptions; Risks with likelihood and impact; Open questions; Out of scope; Stakeholders and approvals; Milestones; and a Change log table (date, change, reason). Number requirements (R-04) so people can reference them in comments, and number open questions (Q1, Q2) linked to the requirement they affect. Make every requirement testable: 'the system shall do X when Y, measured by Z'. If the brief says something vague such as 'fast', write 'TBD: needs a measurable target' and add an open question. Where the brief gives only a goal, write the requirement as a goal with the acceptance condition TBD. Move design ideas to a Notes for design section. Do not add features the brief does not support. If the brief contradicts itself, list the contradiction at the top and do not pick a side without telling me. Show requirement counts by priority with arithmetic, for example 12 must, 7 should and 3 could make 22. End with the five questions that would most reduce risk before the build, a review schedule (who reads, who signs off, when to review after release), and a one-paragraph executive summary short enough for an email.
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.
See an example result (fictional data)
Invented brief: allow customers to download invoices. Requirements table. R-01 Must: a logged-in customer can download a PDF invoice for any completed order; acceptance: PDF contains order number, date, items, tax and total. R-02 Must: a customer cannot see another customer's invoice. R-03 Should: invoices can be downloaded in bulk for a date range. R-04 Could: send invoice by email on request. Open questions: Q1 which tax details must appear (owner: finance)? Q2 how long are invoices kept (owner: legal)? Requirement count: 2 must, 1 should, 1 could, total 4.
Illustrative only, made-up data. Your results will differ and must be reviewed.