test-plan

Invoke the test-plan skill after the functional spec, nonfunctional spec, and architecture document are signed. It generates a complete test plan covering strategy, test levels, environments, schedule, resources, risks, and quality metrics at documentation/09-quality/test-plan.md.

A test plan should include scope, test strategy with levels and types, environment requirements, schedule with entry and exit criteria, deliverables, resource plan, risk management, quality metrics, and defect management. This skill generates all of these sections from a structured template.

Three documents must exist and be signed: the functional specification, the nonfunctional requirements register, and the software architecture document. The skill blocks generation and reports which prerequisite is missing if any are unsigned.

The QA Lead holds final approval authority over the test plan. The Project Manager, Technical Lead, and Product Owner provide required reviews of schedule, technical approach, and business coverage, but their reviews do not gate the signature.

Generation is blocked when a prerequisite document is not signed, the output is not at its canonical path, placeholders remain, or cross-references point to unsigned documents. The validation rules report the specific failure so it can be fixed before requesting sign-off.