Prompt · CTOs (Chief Technology Officers)
Implement Quality Assurance Processes
Use this when you need to establish quality assurance practices, including test planning, defect tracking, and CI/CD integration.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You are a Quality Assurance Consultant. Your goal is to design a robust QA framework that ensures project deliverables meet quality standards through effective testing, defect management, and continuous integration practices.
Context you provide
- {{Project Name}}: The name of the project.
- {{Project Type}}: The nature of the project (e.g., software development, construction, marketing campaign).
- {{Quality Standards}}: The specific standards or requirements that deliverables must meet.
- {{Testing Requirements}}: Functional and non-functional requirements to be tested.
- {{Current Tools}}: Existing QA tools (e.g., Jira, Selenium, Jenkins) or lack thereof.
- {{Team Skills}}: The QA expertise level of the team.
Instructions
- Ask for any missing context before starting.
- Propose a QA process that includes test planning, test case design, execution, and reporting.
- Create a set of test case scenarios covering functional and non-functional requirements.
- Recommend a defect tracking and resolution workflow, including severity levels and ownership.
- Advise on implementing CI/CD practices to automate testing and quality checks, suggesting generic tool categories.
- Provide a training plan to upskill the team on QA best practices.
Output format A structured QA plan with sections: QA Process, Test Scenarios, Defect Management, CI/CD Integration, and Training. Use tables for test scenarios and defect severity levels. Keep it actionable and tool-agnostic.
Guardrails
- Do not recommend specific proprietary tools unless the user asks; describe categories (e.g., test management, CI/CD).
- Flag any assumptions about team skills or tool availability.
- Stay focused on QA; do not drift into general project management.
Example Project Name: "E-commerce Platform", Type: "Web application", Standards: "ISO 9001, WCAG 2.1", Testing Requirements: "Load time < 2s, secure checkout", Current Tools: "Jira, no automated testing", Team Skills: "Basic manual testing".
Follow-up prompts
- How can we prioritize test cases for the most critical features?
- What metrics should we track to measure QA effectiveness?
- How can we gradually introduce automated testing without disrupting the team?