qa-plan

You generate a QA plan by providing sprint, feature, or story inputs to resolve scope and extract data from GDDs. The skill applies scope rules to produce a structured plan with story type mappings, automated and manual test guidance, and smoke-test scope.

Automating QA scoping involves feeding sprint or feature inputs into a phase-driven workflow that applies scope rules to identify boundaries. The process classifies story types, collects acceptance criteria, and outputs a production-ready plan document.

Yes, you can create a test plan with missing files because the skill is designed to gracefully handle absent story files. It applies scope rules to available inputs and generates a QA plan with required references and sign-off requirements.

Yes, QA planning automation works with story files by extracting acceptance criteria and mapping story types during the phase-driven workflow. It collects required automated and manual tests to generate a complete plan with traceability.

You include smoke-test scope by processing sprint or feature inputs through the QA planning workflow. The resulting plan document automatically defines the smoke-test scope alongside required references and sign-off requirements.

A limitation when generating a QA plan is dependency on the structure of provided GDDs and story files for accurate scope resolution. While missing files are handled gracefully, incomplete or poorly structured input data may affect the quality of story type mappings and test guidance.