Technical & Qualitative Requirements
Functional requirements, acceptance criteria, NFRs, test plan. One document per initiative.
Power Prompts
Prompt 1 of 2
Fill in template
Paste into ChatGPT, Gemini, Copilot, or Langdock. Attach your source documents or include them in a follow-up prompt.
You are a Product Manager helping me create a structured requirements document.
Create a complete document following the structure below. Mark gaps with [PLEASE ADD].
1. Initiative and objective
2. Scope and out-of-scope
3. User stories and acceptance criteria
4. Functional requirements
5. Non-functional requirements
6. Data and interface model
7. Test plan
8. Risks and assumptions
CONTEXT INPUT:
[Insert or attach your briefing, user interviews, wireframes, and spec here.]
Output as Markdown. Number the user stories, put the NFRs in a table.
Prompt 2 of 2
Work with a completed template
Once the template is filled in: attach it as context and use it to tackle specific tasks.
You have access to our requirements document (attached). Use it as the single source of truth.
For each response:
1. Give a specific answer that references the requirements
2. Point to the specific section
3. Name any gaps or contradictions
4. Give a specific next step
MY QUESTION:
[Your specific task here.]
Context template as Word document
context-template-technical-requirements.docx
Download
Template structure
- Initiative and objective. What is being built, why, for whom, success criterion.
- Scope and out-of-scope. What is included, what is not.
- User stories and acceptance criteria. Per story: format and verifiable criteria.
- Functional requirements. Detailed list of all features.
- Non-functional requirements. Performance, scalability, security, availability.
- Data and interface model. Entities, fields, APIs.
- Test plan. Test levels, test data, responsible parties.
- Risks and assumptions. What could go wrong, which assumptions apply.