What problem does it solve? Breaking a business capability into individual user experiences is error-prone: journeys get bundled together, seams between journeys mismatch, and drafting starts before the full set is visible. This Skill enumerates the complete set of user experiences implied by a reviewed capability doc and files one GitHub issue per experience so each can be authored individually. ## Core Features & Use Cases - Review Gate Enforcement: Refuses to run unless the capability doc has a reviewed_at frontmatter date newer than the file's last modification, preventing planning against unreviewed drafts. - Grounded Enumeration: Proposes verb-led journey titles with persona and goal, each anchored to specific capability sections (Stakeholders, Triggers, Outputs, Business Rules, Success Criteria), and rejects bundled or cross-capability journeys. - Issue Filing Workflow: After human approval, files one GitHub issue per experience via gh issue create using the repo's story(ux): title convention, wires blocked by ordering edges, and places issues on the project board with milestone and Area set. - Use Case: After reviewing the self-hosted-personal-media-storage capability, invoke this Skill to produce a confirmed list like "upload a photo", "share an album", and "delete content", then file one tracked issue per journey for later authoring via define-user-experience. ## Quick Start Ask the assistant to plan the user experiences for a reviewed capability doc, for example: "Plan the user experiences for the self-hosted-personal-media-storage capability."
