Create User Stories

Overview

Generate a user story map following Jeff Patton's story mapping approach, with BDD-style Given/When/Then acceptance criteria for every story. Stories are grouped by user activity, tagged with priority and complexity, and include dedicated edge-case stories.

Workflow

1. Read product context — Load .chalk/docs/product/0_product_profile.md and any JTBD docs to understand personas, goals, and existing terminology. If no product context exists, work from what the user provides.

2. Locate the PRD — If $ARGUMENTS references a PRD (by path or name), read it. Search .chalk/docs/product/ for PRD files matching the feature. If a PRD exists, it is the primary input. If no PRD exists, accept the feature description from $ARGUMENTS directly and note that stories are being written without a PRD.

3. Identify user activities — Break the feature into 3-7 high-level user activities (the "backbone" in story mapping). Each activity represents a distinct thing the user does to accomplish their goal. Activities are ordered left-to-right by the sequence the user would perform them.

4. Write stories for each activity — Under each activity, write stories from highest to lowest priority. Each story gets:

   • The story statement: "As a [persona], I want [action], so that [outcome]"
   • 2-4 acceptance criteria in Given/When/Then format
   • A priority tag: must (MVP), should (important but not blocking), could (nice-to-have)
   • A complexity tag: S (< 1 day), M (1-3 days), L (3-5 days)