Write a quality management plan for a project or feature
A practical plan defining quality standards, testing, acceptance criteria, reviews, and defect handling before work starts.
The prompt
Help me write a quality management plan for my project.
Project or feature: [WHAT IS BEING BUILT and for whom]
Requirements: [key functional and non-functional requirements, or paste a spec]
Quality expectations: [e.g. "page loads under 2 seconds", "WCAG 2.2 AA", "zero critical defects at launch", internal or client standards]
Team and roles: [who builds, reviews, tests, and signs off]
Timeline and constraints: [deadline, budget, environments available]
Methodology: [agile / waterfall / hybrid]
Write the plan with these sections:
1. Quality objectives: measurable targets tied to the requirements.
2. Standards and definitions: coding, design, accessibility, security, or regulatory standards that apply; Definition of Ready and Definition of Done.
3. Acceptance criteria: testable criteria for each major requirement (use Given/When/Then where it helps).
4. Quality assurance (preventing defects): reviews, pairing, design checks, checklists, and when each happens.
5. Quality control (finding defects): test strategy by level — unit, integration, end-to-end, performance, security, accessibility, user acceptance — with what is automated vs. manual.
6. Defect management: severity and priority definitions, triage process, and exit criteria for release.
7. Metrics and reporting: e.g. defect density, escaped defects, test coverage of requirements, and who sees them how often.
8. Roles and sign-off: a RACI for quality activities.
9. Risks to quality and mitigations.
Keep it concise enough that the team will actually use it. Mark any target I haven't given you as [CONFIRM].
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
- WHAT IS BEING BUILT and for whom
- who builds, reviews, tests, and signs off
- deadline, budget, environments available
- agile / waterfall / hybrid
- CONFIRM
How this prompt is built
This prompt follows the Few-Shot structure (Few-shot prompting). A few-shot prompt includes one or more worked examples of the input and the output you want, so the model can copy the pattern instead of guessing it.
Related prompts
- Find unnecessary approvals in a workflow and simplify sign-offsReviews every approval in a workflow, flags the ones that add delay without reducing risk, and proposes a leaner sign-off design with thresholds.
- Write SMART goals and action steps for a school improvement planTurns needs-assessment data into measurable school improvement goals, strategies, and progress checks.
- Write a sole-source justification that will survive reviewA noncompetitive procurement justification with the legal basis, market research, and price reasonableness that auditors and procurement officers expect.
- Create a role-based IT setup checklist for new hiresBuilds a provisioning checklist per role so every new starter gets the right accounts, devices, and access on day one.