Guide · Agent skill
How to use the Test Scenario Writer agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The Test Scenario Writer is an agent skill named test-scenarios that helps an AI agent turn a user story and its acceptance criteria into detailed written test scenarios. This guide is for QA engineers, product managers and developers who want a first draft of test cases. By the end you will know how to install the skill, how to ask for test scenarios in plain language, and what to check before using the output.
Test Scenario Writerphuryn/pm-skills · MIT Download the skill Quick start
- 1Download the ZIP. Download the test-scenarios ZIP file from this page.
- 2Unzip into a skills folder. Unzip it into ~/.claude/skills/ for personal use or into .claude/skills/ inside a project.
- 3Or upload in the Claude apps. In the Claude apps, go to Settings → Capabilities → Skills and upload the skill.
- 4Gather the user story. Collect the story title, its acceptance criteria, the product name and any testing constraints.
- 5Ask in plain language. Request test scenarios for the story, for example asking for test cases, a test plan or acceptance tests.
- 6Review the output. Check each scenario against the acceptance criteria and add cases the agent missed.
What is an agent skill and what does this one do?
An agent skill is a folder of instructions that an AI agent can load when a task matches the skill's description. This skill is a single file, SKILL.md, containing a fixed process and output template. It is written as instructions only: it does not run any code or access outside systems.
Once the skill is active, the agent takes a user story and its acceptance criteria and produces test scenarios. Each scenario includes a test objective, starting conditions, the user role performing it, numbered steps with expected results, and edge cases such as invalid inputs and boundary conditions.
- Test objective: the specific behavior being validated
- Starting conditions: system state, data setup, configurations and user permissions
- User role: who performs the test actions
- Test steps: numbered actions, each with an expected result
- Expected outcomes: observable results after the steps
- Edge cases: invalid inputs and boundary conditions
How do you install the test-scenarios skill?
Download the ZIP file from this page and unzip it. You can install the skill in one of two places. For all your projects, unzip it into ~/.claude/skills/. For a single project, unzip it into that project's .claude/skills/ folder.
If you use the Claude apps instead, upload the skill under Settings → Capabilities → Skills.
- Personal install: ~/.claude/skills/
- Project install: .claude/skills/ inside your project folder
- Claude apps: Settings → Capabilities → Skills
How do you trigger the skill with a natural request?
You do not need to type a special command. The skill's description says it applies when you are writing QA test cases, creating test plans, defining acceptance tests or preparing for feature validation. Describe that task in your own words and include the user story and its acceptance criteria.
The skill's template uses three inputs: the product or system name, the user story to test (title and acceptance criteria), and any extra testing context or constraints. Including all three usually gives better scenarios.
- Write test cases for this user story: [title and acceptance criteria]. The product is [name]. Assume the test environment has no payment sandbox.
- Create a test plan for the password reset feature using these acceptance criteria: [paste criteria].
- Define acceptance tests for this story and include invalid inputs and boundary conditions: [paste story].
What does a finished test scenario look like?
The skill follows a fixed template, so each scenario has the same parts in the same order. This consistency makes the output easier for a QA team to review and run. The included example is a scenario named View Recently Viewed Products on Product Page, with a test objective, three starting conditions, the Online Shopper role, five numbered steps and six expected outcomes.
The skill's deliverables list says the output covers each acceptance criterion, states test objectives aligned with the user story intent, gives observable outcomes after each step, and includes edge case and error coverage.
What should you check before using the output?
Treat the output as a first draft. The skill's own assessment notes that the output is unreviewed AI text and can miss cases. Read each scenario against the original acceptance criteria, confirm the starting conditions match your real test environment, and add cases the agent did not think of.
The skill produces written scenarios, not runnable test scripts, so you will still need your test framework to automate anything. For safety-critical or regulated testing, have a qualified person validate the scenarios before they are used.
- Compare every scenario with the acceptance criteria it claims to cover
- Confirm starting conditions and data setup match your environment
- Add missing cases, especially for your business rules
- Have a qualified human sign off for safety-critical or regulated work
What does the skill need and what are the safety notes?
The skill lists no requirements. It does not run scripts and does not use the network. Because it is instructions only, it reads the text you give it and writes scenarios from that text. Keep in mind that anything you paste into the agent is part of the conversation, so avoid pasting confidential data you are not permitted to share.
- Requires: nothing listed
- Runs scripts: no
- Uses network: no
What people use it for
- QA engineers drafting first-pass test cases from a feature spec
- Product managers checking that acceptance criteria are testable
- Developers preparing acceptance tests before or after building a feature
- Teams standardising test scenario format across stories using the fixed template
Frequently asked questions
Is the test-scenarios skill free?
The source lists the licence as MIT. Check the licence file in the repository for the full terms before you use or redistribute it.
What does the test-scenarios skill require?
The skill lists no requirements. It runs no scripts and uses no network access, and it is made of instructions only.
Where do I install the test-scenarios skill?
Unzip the downloaded ZIP into ~/.claude/skills/ for personal use or into .claude/skills/ in a project. In the Claude apps, upload it under Settings → Capabilities → Skills.
Does this skill generate automated test code?
No. It produces written test scenarios, not runnable test scripts, so it will not replace a test framework.
Can I use it for safety-critical or regulated testing?
It is not recommended on its own. The output is unreviewed AI text and can miss cases, so a qualified human should validate the scenarios for safety-critical or regulated testing.
How is this different from writing test cases by hand?
The skill gives you a fixed first draft in a consistent template, with objectives, starting conditions, roles, steps and edge cases. You still need to review and extend it, because it can miss cases.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
Use this skill if you need a fast, consistently structured first draft of test scenarios from user stories and acceptance criteria. Pick something else if you need runnable automated tests or validated scenarios for safety-critical or regulated systems.
Download the skill