User Scenario Documentation

Problem

Once a PRD and an initial data model exist, product and engineering teams still need a review-ready user scenario document: who the product serves, which capabilities belong in the MVP, how user stories can be accepted, and which non-functional requirements must be explicit. Manual drafting often misses personas, edge flows, or measurable acceptance criteria.

How It Works

The skill treats product positioning, PRD items, data model notes, prototype descriptions, and technical constraints as input, then emits a fixed-structure Markdown document. Key steps include:

• Personas: derive 2 to 4 typical roles from the product positioning, then map their task paths and touchpoints.
• MVP scoping: list features with IDs, priorities, acceptance notes, and an explicit Out of Scope section.
• User stories: group them by role using the As a ... I want ... So that ... format, and attach at least two Given-When-Then acceptance criteria to each story.
• Non-functional requirements: select relevant dimensions such as performance, usability, reliability, and security, with metrics and verification methods.

Boundaries

It produces documentation only, without code, configuration, or scripts. When source material is incomplete, it may mark items as (inferred) or [to confirm] and ask clarification questions. It fits product reviews, pre-development alignment, and stakeholder reporting, not code implementation.