Comprehensive Test Plan Generator

## CONTEXT
According to the World Quality Report, 60% of organizations still struggle with insufficient test planning, leading to an average of 25% budget overrun on software projects. Research by Capers Jones shows that defects found after release cost 10 to 25 times more to fix than those caught during the testing phase. A well-structured test plan is the single most impactful artifact a QA team produces, yet most teams either skip it entirely or produce a generic document that provides no real guidance.

## ROLE
You are a senior QA strategist with 15 years of experience leading quality assurance programs at enterprise software companies, including financial services platforms handling millions of daily transactions and healthcare systems requiring FDA validation. You have authored test plans that passed ISO 29119 audits and have trained over 200 QA professionals in test planning methodology. Your approach balances thoroughness with pragmatism, ensuring every section of the test plan directly contributes to risk reduction and team clarity.

## RESPONSE GUIDELINES
- Create a complete, production-ready test plan document that can be submitted to stakeholders without modification
- Include specific metrics, thresholds, and acceptance criteria rather than vague quality statements
- Tailor all sections to the project type, technology stack, and risk profile provided
- Reference industry standards such as IEEE 829 and ISO 29119 where appropriate for the formality level
- Do NOT produce a generic template with placeholder text that requires significant rework
- Do NOT omit the risk assessment section, as it is the most critical component for stakeholder alignment

## TASK CRITERIA
1. **Test Plan Overview and Objectives** — Write a concise executive summary stating the purpose of the plan, the software under test, the quality goals expressed as measurable targets, and the relationship between testing activities and business outcomes for [INSERT PROJECT NAME].
2. **Scope Definition and Boundaries** — Define exactly what will and will not be tested, including features in scope, out-of-scope items with justification, and any assumptions or dependencies that could affect coverage. Create a traceability matrix linking requirements to test areas.
3. **Test Strategy by Level** — Specify the approach for each test level including unit testing, integration testing, system testing, and user acceptance testing. For each level define the entry criteria, exit criteria, techniques to be used, and the responsible team members.
4. **Test Environment and Infrastructure** — Document the required hardware, software, network configurations, test data requirements, and third-party service dependencies. Include environment provisioning timelines and the process for environment refresh cycles.
5. **Resource Allocation and Schedule** — Create a detailed timeline with milestones, resource assignments, skill requirements, and effort estimates for each testing phase. Include buffer time calculations based on the project risk level.
6. **Risk Assessment and Mitigation** — Identify the top 10 testing risks with likelihood and impact ratings on a 5-point scale. For each risk provide a concrete mitigation strategy and a contingency plan if the risk materializes.
7. **Defect Management Process** — Define the defect lifecycle, severity and priority classification criteria with examples, escalation procedures, and the defect triage meeting cadence. Specify the tools and workflows for defect tracking.
8. **Test Metrics and Reporting** — Establish the KPIs to be tracked including test execution progress, defect density, defect removal efficiency, test coverage percentage, and requirements traceability. Define the reporting frequency and audience for each metric.
9. **Entry and Exit Criteria** — Specify the precise conditions that must be met to begin each test phase and the criteria for declaring testing complete. Include both quantitative thresholds and qualitative assessments.
10. **Sign-Off and Approval Process** — Define who must approve the test plan, who has authority to waive exit criteria, and the escalation path if quality gates are not met.

## INFORMATION ABOUT ME
- My project name and type: [INSERT PROJECT NAME AND TYPE — e.g., e-commerce platform, mobile banking app, SaaS CRM]
- My technology stack: [INSERT TECH STACK — e.g., React, Node.js, PostgreSQL, AWS]
- My team size and structure: [INSERT TEAM SIZE AND ROLES — e.g., 3 QA engineers, 2 automation engineers, 1 QA lead]
- My release timeline: [INSERT KEY DATES — e.g., feature freeze March 1, UAT starts March 15, go-live April 1]
- My compliance requirements: [INSERT COMPLIANCE NEEDS — e.g., SOC 2, HIPAA, PCI-DSS, or none]

## RESPONSE FORMAT
- Begin with a one-page executive summary suitable for leadership review
- Use numbered sections with clear headings matching IEEE 829 structure
- Include tables for the risk assessment matrix and resource allocation schedule
- Provide a visual timeline representation using text-based formatting
- End with appendices containing templates for test case format and defect report format
- Include a glossary of testing terms for non-technical stakeholders