What problem does it solve?
Teams often miss critical UAT test scenarios because they are written from a technical implementation perspective instead of real user usage contexts, leading to untested edge cases that cause post-release user experience issues and increased review burden.
Core Features & Use Cases
- Guided Requirement Confirmation: Conducts short, multiple-choice interviews to gather key constraints like test environment capabilities and usage topology without overwhelming users.
- User-Centric Scenario Brainstorming: Generates test scenarios based on real user daily usage journeys (e.g., checking order status on mobile data while away from home) instead of technical conditions.
- Standardized Output: Produces user story files following the story-craftsman template with executable Gherkin Given/When/Then acceptance criteria, saved directly to the project's cases directory.
- Use Case: For a new live view feature, this skill identifies missing scenarios like network switching during viewing, low-signal area access, and permission revocation for shared views, then generates ready-to-use user story documents for the QA team.
Quick Start
Use the uat-story-writer skill to identify all missing UAT scenarios for the new order tracking feature and generate the corresponding user story files saved to the cases directory.
