Click Test Plan
Plan first-click, navigation, and five-second tests so you can measure whether users find key tasks in your UI before you ship.
Overview
Click Test Plan is an agent skill most often used in Validate (also Build, Ship) that designs first-click and navigation tests to measure information findability in prototypes and live UI.
Install
npx skills add https://github.com/owl-listener/designer-skills --skill click-test-planWhat is this skill?
- Covers four test types: first-click, click-path, navigation, and five-second recall
- Five-part plan: objective, stimuli, tasks, success criteria, and participant sizing (often 20–50 for quantitative runs)
- Success metrics include first-click target areas, time to first click, confidence ratings, and heat-map-style click dist
- Analysis playbook with 65%+ first-click success as a findability benchmark
- Best-practice guardrails: one task per screen and pre-defined click targets
- Four test types: first-click, click-path, navigation, five-second
- Five-section test plan structure
- 65%+ first-click success cited as good findability indicator
Adoption & trust: 562 installs on skills.sh; 1.5k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have screens or a prototype but no rigorous plan to know if users can find features and whether your navigation structure actually works.
Who is it for?
Solo builders and small teams validating nav labels, settings placement, or core task paths on Figma-linked or staged builds before release.
Skip if: Teams with no visual stimuli yet (use IA research first) or projects that only need backend/API contract tests.
When should I use this skill?
Design click/first-click tests to evaluate navigation and information findability.
What do I get? / Deliverables
You leave with a repeatable click-test protocol—tasks, targets, sample size, and analysis criteria—ready to run in your testing tool and feed IA fixes before launch.
- Click test plan with objectives, tasks, and success criteria
- Participant and segmentation spec for quantitative runs
- Analysis framework for success rate, time, and confidence
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is validate/prototype because click tests usually run on screens or prototypes to de-risk navigation before full build and launch. Prototype subphase is where findability and IA are tested with stimuli and task scripts without needing production traffic.
Where it fits
Draft first-click tasks for a settings screen before recruiting 30 participants on a Figma prototype.
Re-test nav after renaming primary menu items on a staging SaaS dashboard.
Run a navigation test on production-like UI as a launch gate for ecommerce checkout paths.
How it compares
Use for quantitative findability on fixed screens instead of open-ended interview scripts or automated unit tests.
Common Questions / FAQ
Who is click-test-plan for?
Product designers, indie founders, and agent-assisted builders who want measurable navigation tests without hiring a full UX research team.
When should I use click-test-plan?
During validate/prototype when testing wireframes, after build/frontend when revising nav, and pre-ship when you need a last check on findability before launch.
Is click-test-plan safe to install?
It is documentation-only planning guidance with no runtime permissions; review the Security Audits panel on this catalog page before installing any skill from the repo.
SKILL.md
READMESKILL.md - Click Test Plan
# Click Test Plan You are an expert in designing click tests that evaluate findability and navigation clarity. ## What You Do You design first-click and click tests that measure whether users can find information and features. ## Test Types - **First-click test**: Where do users click first for a given task? - **Click-path test**: Full sequence of clicks to complete a task - **Navigation test**: Can users find items using the nav structure? - **Five-second test**: What do users remember after 5 seconds? ## Test Plan Structure ### 1. Objective What navigation or findability question are you answering? ### 2. Stimuli Screen designs or prototypes to test. Identify which pages/states to show. ### 3. Tasks Clear, goal-oriented tasks without UI hints. Example: 'Where would you click to change your email address?' ### 4. Success Criteria - Correct first click (target area defined) - Time to first click - Confidence rating - Click distribution heat map ### 5. Participants Number needed (typically 20-50 for quantitative), recruitment criteria, any segmentation. ## Analysis - First-click success rate (above 65% generally indicates good findability) - Click distribution patterns - Time analysis (hesitation indicates confusion) - Confidence correlation with accuracy ## Best Practices - Test one task per screen - Define click target areas before testing - Use realistic content, not lorem ipsum - Don't give hints in task wording - Compare alternative designs with same tasks