story▌

Write user stories with clear acceptance criteria to guide development from the user's perspective. \n \n Provides a structured template covering user role, desired action, business value, and detailed acceptance criteria using Given-When-Then format \n Includes reference guides for story refinement, splitting, estimation, and acceptance criteria examples \n Emphasizes user-focused writing, testability, and small story sizing appropriate for single-sprint completion \n Covers best practices for

You are a writing coach. Your role is to help writers develop their own work through questions, diagnosis, and guided exploration. You never write their story for them.

Interactive workshop that transforms flat backlogs into visual story maps organized by user workflow and release priority. \n \n Guides product managers through five adaptive questions to define scope, identify users, generate backbone activities, prioritize user tasks, and plan release slices \n Produces a two-dimensional map with horizontal narrative flow (activities left-to-right) and vertical priority (must-have to nice-to-have top-to-bottom) \n Identifies the walking skeleton—minimal end-to

Break large stories and epics into smaller, independently deliverable increments using eight systematic splitting patterns. \n \n Provides eight splitting patterns: workflow steps, business rule variations, data variations, acceptance criteria complexity, major effort, external dependencies, DevOps steps, and Tiny Acts of Discovery for unpacking unknowns \n Emphasizes vertical slicing (each split delivers complete user value) rather than horizontal task decomposition or arbitrary chopping \n Inc

Hierarchical user journey visualization that breaks activities into steps and tasks, organized left-to-right as narrative flow. \n \n Structures work across two axes: horizontal timeline of user activities (backbone, steps, tasks) and vertical priority levels (MVP to future releases) \n Organizes around user goals and behaviors rather than features or engineering modules, enabling shared understanding across product, design, and engineering teams \n Includes segment, persona, and narrative conte

Translate user needs into development-ready stories with Mike Cohn format and Gherkin acceptance criteria. \n \n Combines \"As a / I want / so that\" user story structure with \"Given / When / Then\" acceptance criteria for testable, outcome-focused work \n Includes quality checks and anti-patterns to avoid generic personas, vague outcomes, and scope creep \n Designed for backlog grooming, sprint planning, and shared understanding between product, engineering, and QA \n Emphasizes stories as con

ln-400-story-executor

ln-220-story-coordinator

Identify what state a story is in and what it needs to move forward. This is not a linear process but a diagnostic model: Assess → Diagnose → Intervene → Reassess.