What problem does it solve? Turning a backlog of user stories into a coherent visual story map is slow and error-prone when done by hand. This Skill produces structured story maps in the Jeff Patton format — personas, epics, prioritized user stories with Gherkin acceptance criteria — and renders them as Markdown documents, Mermaid PDF diagrams, drawio boards, and Lucidspark boards. ## Core Features & Use Cases - Story map generation: Produces paired Markdown and JSON artifacts under docs/story-map/ with epics, personas, priorities, and Gherkin acceptance criteria, following a US-N01 numbering convention. - Two board formats: Format 1 zonal overview boards for discovery and executive framing, and Format 2 per-feature sizing breakdowns with T-shirt estimates ([XXS]–[XXL]) for refinement and sprint planning. - Technical story maps: Derives enabling technical stories (Apex, Mule, Flow, LWC, Config, Framework) under each functional story in a dual-layer layout, with color-coded stickies and fit-to-content banners. - Rendering and board sync: Renders Mermaid diagrams to PDF via mermaid-cli with truncation-safe CSS, renders drawio boards via sf setup-agents diagram render, and manages Lucidspark boards with create/update/reflow modes backed by an item-ID cache. - Use Case: A business analyst asks for a story map of a Salesforce field-service project; the Skill writes docs/story-map/field-service.md and .json, renders a PDF overview, and creates a Lucidspark board with personas, epics, and prioritized stories. ## Quick Start Ask the assistant to create a story map for your project with its epics and user stories, and it will generate the Markdown, JSON, and rendered board under docs/story-map/.