arndvs/ux-validate-flow
skills/ux-validate-flow/SKILL.md
Step 3.3 of Sketch the Solution. Cross-check flow diagram against user stories to find gaps. Use when asked to 'validate flow', 'test user flow', 'check flow against stories', or 'flow validation'.
testing
Updated Apr 30, 2026
$ install --global
skillsauthnpx skillsauth add arndvs/ctrlshft ux-validate-flowInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 30, 2026, 2:38 AM17.0s1 file scanned
SKILL.md
- name:
- ux-validate-flow
- description:
- Step 3.3 of Sketch the Solution. Cross-check flow diagram against user stories to find gaps. Use when asked to 'validate flow', 'test user flow', 'check flow against stories', or 'flow validation'.
UX Step 3.3 — Validate with User Stories
Output "Read UX Validate Flow skill." to chat to acknowledge you read this file.
Phase: /ux-flow-diagram → Step 3 of 3
Read each user story and trace the path through the flow diagram. Identify missing screens, dead ends, and friction points.
Process
-
For each user story, trace the user's journey through the flow:
- What screen do they start on?
- What do they do at each step?
- Can they reach their goal via the available screens?
- How many screens/clicks to reach their goal?
-
Log each validation:
## Flow Validation Log
### [Avatar]'s Story: [Goal]
- **Entry:** Landing Page
- **Path:** Landing → Login → Dashboard → Content Feed → Search → View Content
- **Goal reached:** ✓ Yes / ✗ No
- **Gaps found:** [e.g., "No comment feature — user expects to reply but no screen supports it"]
- **Friction:** [e.g., "3 clicks to reach content — could be 2"]
-
Fix gaps — add missing screens or paths to the flow diagram
-
Identify MVP scope — highlight which screens/paths are essential for V1:
## MVP Scope
| Screen | MVP? | Rationale |
|--------|------|-----------|
| Landing | ✓ | Entry point |
| Login | ✓ | Required |
| Dashboard | ✓ | Core experience |
| Reports | ✗ | V2 — nice to have |
Rules
- Every user story must have a complete, traceable path through the flow
- Gaps found = screens or features to add (iterate the flow diagram)
- MVP = what's definitely not going to change + most benefit for least effort
- Promise the vision, deliver incrementally
Output
Append to flow-diagram.md: Validation Log, Gap Analysis, and MVP Scope table.
Related Skills
arndvs/visual-feedback
development
VerifiedTrustedCommunity
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.
SKILL.mdUpdated May 21, 2026
arndvs/press1-check
development
VerifiedTrustedCommunity
Use when Claude Code sessions had many manual approval ("press 1") prompts or when auditing hook permissions; identifies which Bash commands required approval.
SKILL.mdUpdated May 21, 2026
arndvs/plan-archive
tools
VerifiedTrustedCommunity
Use after merging a PR or during periodic cleanup to archive plan-mode files by linking them to merged PRs.
SKILL.mdUpdated May 21, 2026
arndvs/grill-with-docs
testing
VerifiedTrustedCommunity
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.
SKILL.mdUpdated May 21, 2026