qa-planning

Generate numbered Gherkin scenarios and acceptance criteria for QA contracts.

341|48|Updated Apr 4, 2025
One-click install
npx skills add https://github.com/WellApp-ai/Well --skill qa-planning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-planning
Source: https://github.com/WellApp-ai/Well/tree/main/cursor-rules/skills/qa-planning
Command: npx skills add https://github.com/WellApp-ai/Well --skill qa-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The qa-planning skill automates the creation of a comprehensive QA contract by generating exhaustively numbered Gherkin scenarios (G#N) and corresponding acceptance criteria (AC#N).

Core Features & Use Cases

  • Automated QA Contract: Produces a complete set of Gherkin scenarios and acceptance criteria mapped to feature data sources.
  • Phase-driven Planning: Supports Ask mode Phase 2 convergence, feature scoping, and QA handoff with clear traceability to Plan Mode.
  • Traceability & Reuse: Each G#N/AC#N is reusable across commits and qa-commit validation.

Quick Start

Use this skill to generate a QA contract for a new feature by specifying the feature name and data sources, for example "QA planning for user authentication" to receive a complete G#N/AC#N-based contract.

Frequently Asked Questions about qa-planning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I auto-generate Gherkin scenarios and acceptance criteria for feature planning?

You can auto-generate Gherkin scenarios and acceptance criteria by specifying a feature name and its data sources. The skill maps pre-conditions and expected outcomes into a structured QA contract with exhaustively numbered G#N and AC#N identifiers.

What is a QA contract and when do I need numbered Gherkin scenarios for test automation?

A QA contract is a structured set of testable Gherkin scenarios and acceptance criteria mapped to feature data sources. You need it during feature scoping, convergence, and QA handoff to ensure traceability and enable automated test validation.

How do I create traceable acceptance criteria for QA handoff?

Create traceable acceptance criteria by applying the skill during feature convergence to map data sources and expected outcomes into AC#N identifiers. This produces a reusable contract that Plan Mode can reference and qa-commit can validate.

Can I reuse generated Gherkin scenarios across multiple test automation commits?

Yes, generated Gherkin scenarios are designed for reuse across commits. Each G#N and AC#N identifier in the QA contract remains stable, allowing subsequent qa-commit validation phases to reference the same structured scenarios.

Does qa-planning require any specific dependencies to map data sources into a testable contract?

No external dependencies are required. The skill independently processes feature names and data sources to map pre-conditions and expected outcomes into the numbered Gherkin scenarios and acceptance criteria contract.

Why use numbered Gherkin scenarios instead of standard manual test cases?

Numbered Gherkin scenarios provide strict traceability for QA handoff and automated validation. The G#N and AC#N identifiers allow Plan Mode and qa-commit to programmatically reference specific outcomes, which manual test cases lack.