skills/ux-write-user-story/SKILL.md
Step 1.2 of Sketch the Solution. Write pain-state user stories for each avatar. Use when asked to 'write user story', 'pain story', 'user narrative', or 'describe user journey'.
npx skillsauth add arndvs/ctrlshft ux-write-user-storyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Output "Read UX Write User Story skill." to chat to acknowledge you read this file.
Phase: /ux-user-stories → Step 2 of 3
Write narrative-form user stories that describe each avatar's CURRENT challenge end-to-end. Stories describe pain, not your solution.
For each avatar/goal pair, write a story that:
Write from multiple perspectives. If a user posts something and another user responds, write BOTH sides.
Dig for depth — find "the need behind the need":
Generate both formats:
Narrative format:
### [Avatar Name]'s Story: [Goal]
[Full narrative paragraph describing current-state pain, step by step]
Formal template:
As a [user role], I want to [verb-centric behavior], so that [user value added].
Append to user-stories.md: User Stories section with narrative + formal template per avatar/goal.
development
Use when implementing UI, checking dark/light mode, or validating animations — adds a visual feedback loop via browser screenshots so frontend changes are verified, not assumed.
development
Use when Claude Code sessions had many manual approval ("press 1") prompts or when auditing hook permissions; identifies which Bash commands required approval.
tools
Use after merging a PR or during periodic cleanup to archive plan-mode files by linking them to merged PRs.
testing
Use when stress-testing a plan against the project's domain model — grills the design, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise.