UAT Story Writer

Discover missing UAT test scenarios from real user usage contexts and output structured user story documents.

Core philosophy: UAT tests start from user stories, not from technical implementation. "Checking order status while on the go" reveals real needs better than "HTTP API test."

Rules

1. User perspective first: Each scenario must correspond to a real user behavior or usage context, not a technical condition. Technical conditions are the scenario's background, not the scenario itself
2. Do not fabricate when information is lacking: Key constraints like test environment capabilities and actual topology must be obtained through interviews, not assumed
3. Acceptance criteria must be executable: Each AC uses Gherkin Given/When/Then format, ensuring automation tools can directly consume them
4. Output to cases/ directory: User stories go in the project's cases/ directory; features/ directory is reserved for AI-generated executable automation cases
5. Follow story-craftsman template: File structure strictly follows the story-craftsman template format (background, goals, roles, user stories, progress, update log)

Execution Flow

Step 1: Explore Existing Test Coverage