QA
Risk-based test plan generator
Build a test strategy from an RFC or implementation plan, prioritizing the highest-risk user flows, integrations, and regressions.
qa-planningrisk-based-testingtest-strategyrfcintegration-testinge2e
[ workflow / qa ]
Risk-based test plan generator
Cosmos turns ambiguous QA expectations into a concrete, risk-ranked test plan. It reads the RFC and repo context, finds risky flows and integrations, proposes unit, integration, and end-to-end coverage, then creates implementation-ready test work with explicit ownership and scope.
07 nodes
06 edges
Trigger[trigger]
RFC ready for QA planning
Spec / plan enters test design
AI Agent step[risk]
Identify risky flows
Critical paths · edge cases · regressions
AI Agent step[impact]
Map impacted systems
Code paths · APIs · integrations
AI Agent step[draft]
Draft test strategy
Unit · integration · API · E2E
Human-in-the-loop[approval]
QA lead approval
Scope + priority review
AI Agent step[tickets]
Create test tickets
Coverage goals · owners · environments
Output / Result[output]
Risk-ranked QA plan
Execution-ready test backlog
Workflow prompt
Paste this into Augment to reproduce the workflow end-to-end.
Cosmos, when an RFC or implementation plan is ready for QA planning, generate a risk-based test plan. Read the spec, affected code paths, integrations, historical incidents, customer-critical flows, and recent regressions in the same area. Identify the highest-risk user journeys, edge cases, and third-party dependencies. Draft a scoped plan covering unit, integration, API, and end-to-end tests, including what should be automated versus manual. Create follow-up tickets with clear priorities, expected coverage, environments, and owners so the team can execute the plan before release.