user-stories

A structured aid for writing user stories that follow two well-known agile frameworks: the 3 C's (Card, Conversation, Confirmation) and the INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable). It is intended for product work such as writing user stories, breaking a feature down into backlog items, or defining acceptance criteria. It takes four arguments: the product or system name, the feature to break into stories, a link to design files (Figma, Miro, etc.), and key assumptions or context.

The process is explicit: analyze the feature against the provided design and context, identify user roles and distinct journeys, and apply the 3 C's, a Card (simple title and one-liner), the Conversation (detailed intent), and Confirmation (clear acceptance criteria), while respecting INVEST. It insists on plain language a primary-school graduate could understand and on linking to design files for visual reference. Each generated story uses a consistent template: a title, a description in the classic As a [user role], I want to [action], so that [benefit] form, a design link, and four to six acceptance criteria that are clear, testable, and cover observable behavior, edge cases, and considerations like performance, accessibility, or integration points.

A worked example, a Recently Viewed section on a product page, shows the expected level of specificity, with criteria describing exactly when the section appears, which products are excluded, what each card shows, and what happens on click. The output deliverables are a complete set of independent stories for the feature, each sized to fit within a single sprint and cross-referencing related design documentation, so they can be picked up in any order. A further-reading link to a longer user-story guide is included for teams that want more background.