[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75MRZRHDK8QWDKG4SNMXFVB":3,"skill-same:01M75MRZRHDK8QWDKG4SNMXFVB":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M75MRZRHDK8QWDKG4SNMXFVB","user-story-mapping",null,"Create a user story map that lays out activities, steps, tasks, and release slices. Use when planning a workflow, backlog, or MVP around the user journey.","whimzyLive\u002Fnightshift-ai","whimzyLive","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F22066605?v=4","01M75MMH22XX6R3NTAFHD7HEN7","Rushi Patel","01M75MMH32DHVVC61XRSHWVEV2",3,"MIT","https:\u002F\u002Fgithub.com\u002FwhimzyLive\u002Fnightshift-ai\u002Fblob\u002Fmain\u002Fplugins\u002Fsdlc\u002Fskills\u002Fuser-story-mapping\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: user-story-mapping\ndescription: Create a user story map that lays out activities, steps, tasks, and release slices. Use when planning a workflow, backlog, or MVP around the user journey.\nintent: >-\n  Visualize the user journey by creating a hierarchical map that breaks down high-level activities into steps and tasks, organized left-to-right as a narrative flow. Use this to build shared understanding across product, design, and engineering, prioritize features based on user workflows, and identify gaps or opportunities in the user experience.\ntype: component\n---\n\n## Purpose\n\nVisualize the user journey by creating a hierarchical map that breaks down high-level activities into steps and tasks, organized left-to-right as a narrative flow. Use this to build shared understanding across product, design, and engineering, prioritize features based on user workflows, and identify gaps or opportunities in the user experience.\n\nThis is not a backlog—it's a strategic artifact that shows _how_ users accomplish their goals, which then informs _what_ to build.\n\n## Key Concepts\n\n### The Jeff Patton Story Mapping Framework\n\nInvented by Jeff Patton, story mapping organizes work into a 2D structure:\n\n**Horizontal axis (left-to-right):** User journey over time\n\n- **Backbone:** High-level activities the user performs\n- **Steps:** Specific actions within each activity\n- **Tasks:** Detailed work required to complete each step\n\n**Vertical axis (top-to-bottom):** Priority and releases\n\n- **Top rows:** Essential tasks (MVP \u002F Release 1)\n- **Lower rows:** Nice-to-have tasks (Future releases)\n\n### Story Map Structure\n\n```\nSegment → Persona → Narrative (User's goal)\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n[Activity 1] → [Activity 2] → [Activity 3] → [Activity 4] → [Activity 5]\n     ↓              ↓              ↓              ↓              ↓\n  [Step 1.1]     [Step 2.1]     [Step 3.1]     [Step 4.1]     [Step 5.1]\n  [Step 1.2]     [Step 2.2]     [Step 3.2]     [Step 4.2]     [Step 5.2]\n  [Step 1.3]     [Step 2.3]     [Step 3.3]     [Step 4.3]     [Step 5.3]\n     ↓              ↓              ↓              ↓              ↓\n  [Task 1.1.1]   [Task 2.1.1]   [Task 3.1.1]   [Task 4.1.1]   [Task 5.1.1]\n  [Task 1.1.2]   [Task 2.1.2]   [Task 3.1.2]   [Task 4.1.2]   [Task 5.1.2]\n  [Task 1.1.3]   [Task 2.1.3]   [Task 3.1.3]   [Task 4.1.3]   [Task 5.1.3]\n  ...            ...            ...            ...            ...\n```\n\n### Why This Works\n\n- **User-centric:** Organizes work around user goals, not engineering modules\n- **Shared understanding:** Product, design, engineering all see the same journey\n- **Prioritization clarity:** Top tasks = MVP, lower tasks = future iterations\n- **Gap identification:** Missing steps or tasks become obvious\n- **Release planning:** Draw horizontal \"release lines\" to define scope\n\n### Anti-Patterns (What This Is NOT)\n\n- **Not a Gantt chart:** This isn't project management—it's user journey visualization\n- **Not a feature list:** Activities aren't features—they're user behaviors\n- **Not static:** Story maps evolve as you learn more about users\n\n### When to Use This\n\n- Kicking off a new product or major feature\n- Aligning stakeholders on user workflow\n- Prioritizing backlog based on user needs\n- Identifying MVP vs. future releases\n- Onboarding new team members to the product vision\n\n### When NOT to Use This\n\n- For trivial features (don't map what you already understand)\n- When user workflows are constantly changing (map stabilizes workflows)\n- As a replacement for user stories (the map informs stories, doesn't replace them)\n\n---\n\n## Application\n\n### Step 1: Define the Context\n\nUse `template.md` for the full fill-in structure.\n\n#### Segment\n\nWho are you building for?\n\n```markdown\n### Segment:\n\n- [Specify the target segment, e.g., \"Small business owners using DIY accounting software\"]\n```\n\n**Quality checks:**\n\n- **Specific:** Not \"users\" but \"enterprise IT admins\" or \"freelance designers\"\n\n---\n\n#### Persona\n\nProvide details about the persona within this segment (reference `skills\u002Fproto-persona\u002FSKILL.md`).\n\n```markdown\n### Persona:\n\n- [Describe the persona: demographics, behaviors, pains, goals]\n```\n\n**Example:**\n\n- \"Sarah, 35-year-old freelance graphic designer, manages 5-10 client projects at once, struggles with invoicing and payment tracking, wants to spend less time on admin and more time designing\"\n\n---\n\n### Step 2: Define the Narrative\n\nWhat is the user trying to accomplish? Frame this as a Jobs-to-be-Done statement (reference `skills\u002Fjobs-to-be-done\u002FSKILL.md`).\n\n```markdown\n### Narrative:\n\n- [Concise narrative of the persona's objective, e.g., \"Complete a client project from kickoff to final payment\"]\n```\n\n**Quality checks:**\n\n- **Outcome-focused:** Not \"use the product\" but \"deliver a client project on time and get paid\"\n- **One sentence:** If it takes more than one sentence, the scope may be too broad\n\n---\n\n### Step 3: Identify Activities (Backbone)\n\nList 3-5 high-level activities the persona engages in to fulfill the narrative. These form the backbone of your map.\n\n```markdown\n### Activities:\n\n1. [Activity 1, e.g., \"Negotiate project scope and pricing\"]\n2. [Activity 2, e.g., \"Execute design work\"]\n3. [Activity 3, e.g., \"Deliver final assets to client\"]\n4. [Activity 4, e.g., \"Send invoice and receive payment\"]\n5. [Activity 5, optional]\n```\n\n**Quality checks:**\n\n- **Sequential:** Activities happen in order (left-to-right)\n- **User actions:** Describe what the user _does_, not what the product _provides_\n- **3-5 activities:** Too few = oversimplified, too many = overwhelming\n\n---\n\n### Step 4: Break Activities into Steps\n\nFor each activity, list 3-5 steps that detail how the activity is carried out.\n\n```markdown\n### Steps:\n\n**For Activity 1: [Activity Name]**\n\n- Step 1: [Detail step 1, e.g., \"Review client brief\"]\n- Step 2: [Detail step 2, e.g., \"Draft project proposal\"]\n- Step 3: [Detail step 3, e.g., \"Negotiate timeline and budget\"]\n- Step 4: [Optional step 4]\n- Step 5: [Optional step 5]\n\n**For Activity 2: [Activity Name]**\n\n- Step 1: [Detail step 1]\n- Step 2: [Detail step 2]\n  ...\n```\n\n**Quality checks:**\n\n- **Actionable:** Each step is something the user does\n- **Observable:** You could watch someone perform this step\n- **Logical sequence:** Steps follow a natural order\n\n---\n\n### Step 5: Break Steps into Tasks\n\nFor each step, list 5-7 tasks that must be completed.\n\n```markdown\n### Tasks:\n\n**For Activity 1, Step 1: [Step Name]**\n\n- Task 1: [Detail task 1, e.g., \"Read client brief document\"]\n- Task 2: [Detail task 2, e.g., \"Identify key deliverables\"]\n- Task 3: [Detail task 3, e.g., \"Note budget constraints\"]\n- Task 4: [Detail task 4, e.g., \"Clarify timeline expectations\"]\n- Task 5: [Detail task 5, e.g., \"List open questions for client\"]\n- Task 6: [Optional task 6]\n- Task 7: [Optional task 7]\n\n**For Activity 1, Step 2: [Step Name]**\n\n- Task 1: [Detail task 1]\n  ...\n```\n\n**Quality checks:**\n\n- **Granular:** Tasks are small, specific actions\n- **User-facing or behind-the-scenes:** Include both (e.g., \"Send email\" and \"Receive confirmation\")\n- **Prioritizable:** You'll prioritize tasks vertically (top = essential, bottom = nice-to-have)\n\n---\n\n### Step 6: Prioritize Vertically\n\nArrange tasks top-to-bottom by priority:\n\n- **Top rows:** MVP \u002F Release 1 (must-have)\n- **Middle rows:** Release 2 (important but not critical)\n- **Bottom rows:** Future \u002F Nice-to-have\n\nDraw horizontal \"release lines\" to demarcate scope.\n\n---\n\n### Step 7: Identify Gaps and Opportunities\n\nReview the map and ask:\n\n- Are there missing steps or tasks?\n- Are there pain points we're not addressing?\n- Are there opportunities to delight users?\n- Do all activities flow logically?\n\n---\n\n## Examples\n\nSee `examples\u002Fsample.md` for a full story map example.\n\n---\n\n## Common Pitfalls\n\n### Pitfall 1: Activities Are Features, Not User Behaviors\n\n**Symptom:** \"Activity 1: Use the dashboard. Activity 2: Generate reports.\"\n\n**Consequence:** You've mapped the product, not the user journey.\n\n**Fix:** Reframe as user actions: \"Activity 1: Monitor project progress. Activity 2: Summarize work for stakeholders.\"\n\n---\n\n### Pitfall 2: Too Many Activities\n\n**Symptom:** 10+ activities across the backbone\n\n**Consequence:** Map becomes overwhelming and loses focus.\n\n**Fix:** Consolidate. If you have 10 activities, you're likely mixing activities with steps. Aim for 3-5 high-level activities.\n\n---\n\n### Pitfall 3: Tasks Are Too Vague\n\n**Symptom:** \"Task 1: Do the thing\"\n\n**Consequence:** Can't prioritize or estimate vague tasks.\n\n**Fix:** Be specific: \"Task 1: Enter client email address in the 'Bill To' field.\"\n\n---\n\n### Pitfall 4: Ignoring Vertical Prioritization\n\n**Symptom:** All tasks at the same level—no MVP vs. future releases defined\n\n**Consequence:** No clarity on what to build first.\n\n**Fix:** Explicitly prioritize. Draw release lines. Force hard choices about what's MVP.\n\n---\n\n### Pitfall 5: Mapping in Isolation\n\n**Symptom:** PM creates the map alone, then presents it to the team\n\n**Consequence:** No shared ownership or understanding.\n\n**Fix:** Map collaboratively. Run a story mapping workshop with product, design, and engineering.\n\n---\n\n## References\n\n### Related Skills\n\n- `skills\u002Fproto-persona\u002FSKILL.md` — Defines the persona for the story map\n- `skills\u002Fjobs-to-be-done\u002FSKILL.md` — Informs the narrative and activities\n- `skills\u002Fuser-story\u002FSKILL.md` — Tasks from the map become user stories\n- `skills\u002Fproblem-statement\u002FSKILL.md` — Problem statement frames the narrative\n\n### External Frameworks\n\n- Jeff Patton, _User Story Mapping_ (2014) — Origin of the story mapping technique\n- Teresa Torres, _Continuous Discovery Habits_ (2021) — Opportunity solution trees (complementary to story maps)\n\n### Dean's Work\n\n- User Story Mapping Prompt (adapted from Jeff Patton's methodology)\n\n### Provenance\n\n- Adapted from `prompts\u002Fuser-story-mapping.md` in the `https:\u002F\u002Fgithub.com\u002Fdeanpeters\u002Fproduct-manager-prompts` repo.\n\n---\n\n**Skill type:** Component\n**Suggested filename:** `user-story-mapping.md`\n**Suggested placement:** `\u002Fskills\u002Fcomponents\u002F`\n**Dependencies:** References `skills\u002Fproto-persona\u002FSKILL.md`, `skills\u002Fjobs-to-be-done\u002FSKILL.md`, `skills\u002Fuser-story\u002FSKILL.md`, `skills\u002Fproblem-statement\u002FSKILL.md`\n","## Purpose\n\nVisualize the user journey by creating a hierarchical map that breaks down high-level activities into steps and tasks, organized left-to-right as a narrative flow. Use this to build shared understanding across product, design, and engineering, prioritize features based on user workflows, and identify gaps or opportunities in the user experience.\n\nThis is not a backlog—it's a strategic artifact that shows _how_ users accomplish their goals, which then informs _what_ to build.\n\n## Key Concepts\n\n### The Jeff Patton Story Mapping Framework\n\nInvented by Jeff Patton, story mapping organizes work into a 2D structure:\n\n**Horizontal axis (left-to-right):** User journey over time\n\n- **Backbone:** High-level activities the user performs\n- **Steps:** Specific actions within each activity\n- **Tasks:** Detailed work required to complete each step\n\n**Vertical axis (top-to-bottom):** Priority and releases\n\n- **Top rows:** Essential tasks (MVP \u002F Release 1)\n- **Lower rows:** Nice-to-have tasks (Future releases)\n\n### Story Map Structure\n\n```\nSegment → Persona → Narrative (User's goal)\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n[Activity 1] → [Activity 2] → [Activity 3] → [Activity 4] → [Activity 5]\n     ↓              ↓              ↓              ↓              ↓\n  [Step 1.1]     [Step 2.1]     [Step 3.1]     [Step 4.1]     [Step 5.1]\n  [Step 1.2]     [Step 2.2]     [Step 3.2]     [Step 4.2]     [Step 5.2]\n  [Step 1.3]     [Step 2.3]     [Step 3.3]     [Step 4.3]     [Step 5.3]\n     ↓              ↓              ↓              ↓              ↓\n  [Task 1.1.1]   [Task 2.1.1]   [Task 3.1.1]   [Task 4.1.1]   [Task 5.1.1]\n  [Task 1.1.2]   [Task 2.1.2]   [Task 3.1.2]   [Task 4.1.2]   [Task 5.1.2]\n  [Task 1.1.3]   [Task 2.1.3]   [Task 3.1.3]   [Task 4.1.3]   [Task 5.1.3]\n  ...            ...            ...            ...            ...\n```\n\n### Why This Works\n\n- **User-centric:** Organizes work around user goals, not engineering modules\n- **Shared understanding:** Product, design, engineering all see the same journey\n- **Prioritization clarity:** Top tasks = MVP, lower tasks = future iterations\n- **Gap identification:** Missing steps or tasks become obvious\n- **Release planning:** Draw horizontal \"release lines\" to define scope\n\n### Anti-Patterns (What This Is NOT)\n\n- **Not a Gantt chart:** This isn't project management—it's user journey visualization\n- **Not a feature list:** Activities aren't features—they're user behaviors\n- **Not static:** Story maps evolve as you learn more about users\n\n### When to Use This\n\n- Kicking off a new product or major feature\n- Aligning stakeholders on user workflow\n- Prioritizing backlog based on user needs\n- Identifying MVP vs. future releases\n- Onboarding new team members to the product vision\n\n### When NOT to Use This\n\n- For trivial features (don't map what you already understand)\n- When user workflows are constantly changing (map stabilizes workflows)\n- As a replacement for user stories (the map informs stories, doesn't replace them)\n\n---\n\n## Application\n\n### Step 1: Define the Context\n\nUse `template.md` for the full fill-in structure.\n\n#### Segment\n\nWho are you building for?\n\n```markdown\n### Segment:\n\n- [Specify the target segment, e.g., \"Small business owners using DIY accounting software\"]\n```\n\n**Quality checks:**\n\n- **Specific:** Not \"users\" but \"enterprise IT admins\" or \"freelance designers\"\n\n---\n\n#### Persona\n\nProvide details about the persona within this segment (reference `skills\u002Fproto-persona\u002FSKILL.md`).\n\n```markdown\n### Persona:\n\n- [Describe the persona: demographics, behaviors, pains, goals]\n```\n\n**Example:**\n\n- \"Sarah, 35-year-old freelance graphic designer, manages 5-10 client projects at once, struggles with invoicing and payment tracking, wants to spend less time on admin and more time designing\"\n\n---\n\n### Step 2: Define the Narrative\n\nWhat is the user trying to accomplish? Frame this as a Jobs-to-be-Done statement (reference `skills\u002Fjobs-to-be-done\u002FSKILL.md`).\n\n```markdown\n### Narrative:\n\n- [Concise narrative of the persona's objective, e.g., \"Complete a client project from kickoff to final payment\"]\n```\n\n**Quality checks:**\n\n- **Outcome-focused:** Not \"use the product\" but \"deliver a client project on time and get paid\"\n- **One sentence:** If it takes more than one sentence, the scope may be too broad\n\n---\n\n### Step 3: Identify Activities (Backbone)\n\nList 3-5 high-level activities the persona engages in to fulfill the narrative. These form the backbone of your map.\n\n```markdown\n### Activities:\n\n1. [Activity 1, e.g., \"Negotiate project scope and pricing\"]\n2. [Activity 2, e.g., \"Execute design work\"]\n3. [Activity 3, e.g., \"Deliver final assets to client\"]\n4. [Activity 4, e.g., \"Send invoice and receive payment\"]\n5. [Activity 5, optional]\n```\n\n**Quality checks:**\n\n- **Sequential:** Activities happen in order (left-to-right)\n- **User actions:** Describe what the user _does_, not what the product _provides_\n- **3-5 activities:** Too few = oversimplified, too many = overwhelming\n\n---\n\n### Step 4: Break Activities into Steps\n\nFor each activity, list 3-5 steps that detail how the activity is carried out.\n\n```markdown\n### Steps:\n\n**For Activity 1: [Activity Name]**\n\n- Step 1: [Detail step 1, e.g., \"Review client brief\"]\n- Step 2: [Detail step 2, e.g., \"Draft project proposal\"]\n- Step 3: [Detail step 3, e.g., \"Negotiate timeline and budget\"]\n- Step 4: [Optional step 4]\n- Step 5: [Optional step 5]\n\n**For Activity 2: [Activity Name]**\n\n- Step 1: [Detail step 1]\n- Step 2: [Detail step 2]\n  ...\n```\n\n**Quality checks:**\n\n- **Actionable:** Each step is something the user does\n- **Observable:** You could watch someone perform this step\n- **Logical sequence:** Steps follow a natural order\n\n---\n\n### Step 5: Break Steps into Tasks\n\nFor each step, list 5-7 tasks that must be completed.\n\n```markdown\n### Tasks:\n\n**For Activity 1, Step 1: [Step Name]**\n\n- Task 1: [Detail task 1, e.g., \"Read client brief document\"]\n- Task 2: [Detail task 2, e.g., \"Identify key deliverables\"]\n- Task 3: [Detail task 3, e.g., \"Note budget constraints\"]\n- Task 4: [Detail task 4, e.g., \"Clarify timeline expectations\"]\n- Task 5: [Detail task 5, e.g., \"List open questions for client\"]\n- Task 6: [Optional task 6]\n- Task 7: [Optional task 7]\n\n**For Activity 1, Step 2: [Step Name]**\n\n- Task 1: [Detail task 1]\n  ...\n```\n\n**Quality checks:**\n\n- **Granular:** Tasks are small, specific actions\n- **User-facing or behind-the-scenes:** Include both (e.g., \"Send email\" and \"Receive confirmation\")\n- **Prioritizable:** You'll prioritize tasks vertically (top = essential, bottom = nice-to-have)\n\n---\n\n### Step 6: Prioritize Vertically\n\nArrange tasks top-to-bottom by priority:\n\n- **Top rows:** MVP \u002F Release 1 (must-have)\n- **Middle rows:** Release 2 (important but not critical)\n- **Bottom rows:** Future \u002F Nice-to-have\n\nDraw horizontal \"release lines\" to demarcate scope.\n\n---\n\n### Step 7: Identify Gaps and Opportunities\n\nReview the map and ask:\n\n- Are there missing steps or tasks?\n- Are there pain points we're not addressing?\n- Are there opportunities to delight users?\n- Do all activities flow logically?\n\n---\n\n## Examples\n\nSee `examples\u002Fsample.md` for a full story map example.\n\n---\n\n## Common Pitfalls\n\n### Pitfall 1: Activities Are Features, Not User Behaviors\n\n**Symptom:** \"Activity 1: Use the dashboard. Activity 2: Generate reports.\"\n\n**Consequence:** You've mapped the product, not the user journey.\n\n**Fix:** Reframe as user actions: \"Activity 1: Monitor project progress. Activity 2: Summarize work for stakeholders.\"\n\n---\n\n### Pitfall 2: Too Many Activities\n\n**Symptom:** 10+ activities across the backbone\n\n**Consequence:** Map becomes overwhelming and loses focus.\n\n**Fix:** Consolidate. If you have 10 activities, you're likely mixing activities with steps. Aim for 3-5 high-level activities.\n\n---\n\n### Pitfall 3: Tasks Are Too Vague\n\n**Symptom:** \"Task 1: Do the thing\"\n\n**Consequence:** Can't prioritize or estimate vague tasks.\n\n**Fix:** Be specific: \"Task 1: Enter client email address in the 'Bill To' field.\"\n\n---\n\n### Pitfall 4: Ignoring Vertical Prioritization\n\n**Symptom:** All tasks at the same level—no MVP vs. future releases defined\n\n**Consequence:** No clarity on what to build first.\n\n**Fix:** Explicitly prioritize. Draw release lines. Force hard choices about what's MVP.\n\n---\n\n### Pitfall 5: Mapping in Isolation\n\n**Symptom:** PM creates the map alone, then presents it to the team\n\n**Consequence:** No shared ownership or understanding.\n\n**Fix:** Map collaboratively. Run a story mapping workshop with product, design, and engineering.\n\n---\n\n## References\n\n### Related Skills\n\n- `skills\u002Fproto-persona\u002FSKILL.md` — Defines the persona for the story map\n- `skills\u002Fjobs-to-be-done\u002FSKILL.md` — Informs the narrative and activities\n- `skills\u002Fuser-story\u002FSKILL.md` — Tasks from the map become user stories\n- `skills\u002Fproblem-statement\u002FSKILL.md` — Problem statement frames the narrative\n\n### External Frameworks\n\n- Jeff Patton, _User Story Mapping_ (2014) — Origin of the story mapping technique\n- Teresa Torres, _Continuous Discovery Habits_ (2021) — Opportunity solution trees (complementary to story maps)\n\n### Dean's Work\n\n- User Story Mapping Prompt (adapted from Jeff Patton's methodology)\n\n### Provenance\n\n- Adapted from `prompts\u002Fuser-story-mapping.md` in the `https:\u002F\u002Fgithub.com\u002Fdeanpeters\u002Fproduct-manager-prompts` repo.\n\n---\n\n**Skill type:** Component\n**Suggested filename:** `user-story-mapping.md`\n**Suggested placement:** `\u002Fskills\u002Fcomponents\u002F`\n**Dependencies:** References `skills\u002Fproto-persona\u002FSKILL.md`, `skills\u002Fjobs-to-be-done\u002FSKILL.md`, `skills\u002Fuser-story\u002FSKILL.md`, `skills\u002Fproblem-statement\u002FSKILL.md`\n",{"name":5,"type":24,"intent":25,"description":7},"component","Visualize the user journey by creating a hierarchical map that breaks down high-level activities into steps and tasks, organized left-to-right as a narrative flow. Use this to build shared understanding across product, design, and engineering, prioritize features based on user workflows, and identify gaps or opportunities in the user experience.","main","7d4ebd573a4218d5e92eced411b259f34e9203fe","plugins\u002Fsdlc\u002Fskills\u002Fuser-story-mapping",0,"https:\u002F\u002Fgithub.com\u002FwhimzyLive\u002Fnightshift-ai","https:\u002F\u002Fwithnightshift.com\u002F","https:\u002F\u002Fgithub.com\u002FwhimzyLive","Creator of @typedorm","2026-11-14 22:45:42",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add whimzyLive\u002Fnightshift-ai --skill user-story-mapping",{"tool":41,"command":42},"bunx","bunx skills add whimzyLive\u002Fnightshift-ai --skill user-story-mapping",{"tool":44,"command":45},"pnpm","pnpm dlx skills add whimzyLive\u002Fnightshift-ai --skill user-story-mapping","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FwhimzyLive\u002Fnightshift-ai\u002Fblob\u002Fmain\u002Fplugins\u002Fsdlc\u002Fskills\u002Fuser-story-mapping\u002FSKILL.md",true,[49,55],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"examples\u002Fsample.md","REFERENCE","参考文档",2200,"https:\u002F\u002Fgithub.com\u002FwhimzyLive\u002Fnightshift-ai\u002Fblob\u002Fmain\u002Fplugins\u002Fsdlc\u002Fskills\u002Fuser-story-mapping\u002Fexamples\u002Fsample.md",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"template.md",1004,"https:\u002F\u002Fgithub.com\u002FwhimzyLive\u002Fnightshift-ai\u002Fblob\u002Fmain\u002Fplugins\u002Fsdlc\u002Fskills\u002Fuser-story-mapping\u002Ftemplate.md",[60,68,75,82,89,96],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":67},"01M7BCEWYHDS1FWAJ6G4CD9P54","designing-in-patterns","Use when designing, planning or auditing UI against a component library — naming surfaces with the repo's pattern vocabulary, deciding reuse versus extend versus new, exploring compositions, or writing the reuse table (component-plan.md, a spec's `## Reuse`, a UI audit). Carries the design method; the repo's own vocabulary, bundle and board rules come from project-context and the designer override.","https:\u002F\u002Fgithub.com\u002FwhimzyLive\u002Fnightshift-ai\u002Fblob\u002Fmain\u002Fplugins\u002Fsdlc\u002Fskills\u002Fdesigning-in-patterns\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M75MVN6GACAC87SV9RBPBMKH","typeorm","Use when defining TypeORM entities, writing migrations, or building repository\u002Fquery-builder code in TypeScript. Covers entity and relation decorators, the Data Mapper pattern, migrations, the query builder, transactions, and multi-database configuration.","https:\u002F\u002Fgithub.com\u002FwhimzyLive\u002Fnightshift-ai\u002Fblob\u002Fmain\u002Fskills\u002Ftypeorm\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M75MTEZV8SAZNS20YDSB7KG2","hono-api","Use when building or extending REST APIs with Hono + @hono\u002Fzod-openapi. Covers schema-first route declaration with createRoute, feature-grouped composable routers, a class-based service layer behind interfaces, the strategy pattern for multi-event webhooks, typed request validation, and auto-generated OpenAPI docs.","https:\u002F\u002Fgithub.com\u002FwhimzyLive\u002Fnightshift-ai\u002Fblob\u002Fmain\u002Fskills\u002Fhono-api\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M75MTB91SB6HPB3ZRT20F950","electrodb","Use when defining DynamoDB entities, modeling indexes, or writing queries\u002Fmutations with the ElectroDB ORM. Covers entity schema, access patterns, CRUD operations, update expressions, and single-table design patterns.","https:\u002F\u002Fgithub.com\u002FwhimzyLive\u002Fnightshift-ai\u002Fblob\u002Fmain\u002Fskills\u002Felectrodb\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M75MT7KT9A3XYX38TX5MY6MA","atomic-design","Use when structuring or decomposing any frontend UI into reusable components, regardless of framework. Applies Brad Frost's atomic design methodology — atoms, molecules, organisms, templates, and pages — to guide consistent component hierarchy, naming, and composition decisions.","https:\u002F\u002Fgithub.com\u002FwhimzyLive\u002Fnightshift-ai\u002Fblob\u002Fmain\u002Fskills\u002Fatomic-design\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M75MSTQ54EY0K29PKBF212K1","writing-docs","Use when writing, restructuring, or reviewing any prose documentation — a tutorial, how-to guide, reference page, or explanation\u002Fconceptual doc — for a public docs site (e.g. Mintlify MDX, docs\u002F, README material), a getting-started guide, an API\u002FCLI reference page, or a \"why we built it this way\" conceptual page. Applies the Diátaxis framework (see https:\u002F\u002Fdiataxis.fr\u002F) — every document belongs to exactly one of the four quadrants (tutorial \u002F how-to guide \u002F reference \u002F explanation), and mixing quadrants inside one document is the single most common documentation failure. Covers the four-quadrant compass for picking the right form, per-quadrant structure templates, an anti-pattern list for quadrant drift, and generic voice\u002Fcraft rules — repo-specific voice and target output format (e.g. Mintlify MDX) are resolved from the repo's docs-manifest (falling back to project-context), never hardcoded here.","https:\u002F\u002Fgithub.com\u002FwhimzyLive\u002Fnightshift-ai\u002Fblob\u002Fmain\u002Fplugins\u002Fsdlc\u002Fskills\u002Fwriting-docs\u002FSKILL.md",[],[]]