What problem does it solve? Teams often jump from a business capability straight to implementation, producing systems that technically work but feel wrong to users. This Skill structures the conversation for defining one end-to-end user experience (persona, goal, entry point, journey, success, edge cases) and saves it as a Hugo/Docsy markdown doc linked to its parent capability. ## Core Features & Use Cases - Structured UX elicitation: Walks through persona, goal, entry point, journey steps, success criteria, and failure modes one dimension at a time, pushing back on technical drift. - Capability-anchored documentation: Reads the parent capability doc first and cites its business rules, stakeholders, and success criteria so the UX stays consistent with established constraints. - Hugo/Docsy publishing: Saves the doc as a page bundle under docs/content/capabilities/{capability}/user-experiences/, uses ref shortcodes for cross-linking, preserves explicit heading anchors, and validates the rendered page with hugo server. - Use Case: After defining a photo-storage capability, ask to define the "share an album" user experience; the Skill interviews you about the persona and journey, then produces a Mermaid-annotated markdown doc linked under that capability. ## Quick Start Ask the assistant to define the user experience for an existing capability, for example: "Define the UX for uploading a photo under the photo-storage capability."
