test-scenarios takes a product name, a user story with its acceptance criteria and any testing context, and produces scenarios a QA team can execute. Each scenario has a name, a test objective, starting conditions, the user role, numbered steps and expected outcomes.
It follows an eight-step process that covers the story, objectives, system state, roles, steps, outcomes, edge cases such as invalid inputs and boundary conditions, and the final write-up.
What You Get
- Test scenarios for each acceptance criterion
- A test objective tied to the intent of the user story
- Starting conditions covering system state, data and permissions
- Step-by-step actions with an observable outcome after each
- Edge case and error scenarios
- Output ready for QA execution and documentation
Common Use Cases
- Writing QA cases for a new feature
- Defining acceptance tests from a user story
- Preparing a feature for validation before release
What Makes It Unique
Each scenario states its starting conditions and user role up front, and every step carries the result expected at that point. Edge cases and error handling are an explicit step in the process.
Under The Hood
The skill is one SKILL.md of instructions with no scripts. It takes the product, user story and context as arguments, reasons from them and writes the scenarios in its reply. It does not read other files or call external services.