QA Workflow
Generate structured test plans for features and systems automatically.
The QA workflow generates a structured test plan for a feature, system, or workflow. It helps teams think through validation coverage before release by identifying critical user paths, edge cases, failure scenarios, and prioritized risk areas.
Instead of writing a test plan from scratch, this workflow provides a disciplined starting point that organizes quality assurance efforts clearly and systematically.
When to Use QA
Use the QA workflow when:
- Developing a new feature
- Preparing for release
- Planning regression coverage
- Reviewing high-risk changes
- Auditing an existing system for test gaps
- Onboarding into an unfamiliar codebase
It is especially useful before creating a pull request or merging significant functionality.
What the Workflow Does
Once executed, the QA workflow analyzes the repository and available context to generate a structured test strategy that includes:
1. Critical User Paths
- Primary workflows users depend on
- High-impact flows such as authentication, payments, or data submission
- Business-critical interactions
2. Edge Cases
- Boundary inputs
- Unexpected states
- Partial or malformed requests
- Concurrent operations
3. Failure Modes
- API errors
- Network failures
- Invalid input handling
- Authorization failures
- Service downtime scenarios
4. Risk-Based Prioritization
Test cases are categorized and prioritized based on:
- User impact
- Security sensitivity
- Likelihood of regression
- Complexity of change
The result is a structured, production-ready test plan rather than a generic checklist.
Full Prefilled Prompt
When selected, the QA workflow inserts the following instruction into the session:
QA: Draft a test plan with critical paths, edge cases, and prioritized bugs. Ask for feature spec or URL if missing.
Before running, you can provide additional context such as:
- Feature specification
- Relevant PRD or design doc
- Application URL
- Deployment environment
- Target user persona
If required context (such as a feature spec or URL) is missing, the agent will request clarification before generating the plan.
Example Use Case
You’ve just implemented a new checkout flow.
- Launch the QA workflow.
- Add context:
- “This feature handles subscription upgrades and coupon codes.”
- Attach the PRD or reference the relevant files.
- Send the prompt.
- Review the generated test plan.
- Use the plan to:
- Write automated tests
- Create manual test cases
- Guide QA validation
This ensures that both obvious and non-obvious scenarios are covered before release.
Scope and Boundaries
The QA workflow:
- Does not modify files automatically
- Does not run tests automatically
- Does not create test code unless you explicitly ask
- Operates within the active project session
It is a planning and validation workflow designed to strengthen quality coverage before execution.