lean-ux — Skills — getagentictools

Q: What does the lean-ux skill do?

Apply lean thinking to UX: hypothesis-driven design, collaborative sketching, and rapid experiments instead of heavy deliverables. Use when the user mentions "Lean UX", "design hypothesis", "outcome over output", "design studio method", "assumption mapping", "lightweight research", "too much design documentation", or "get the team designing together". Also trigger when reducing design-documentation overhead, getting cross-functional teams to co-design, or running fast usability experiments. Covers hypothesis statements, MVPs for UX, and cross-functional collaboration. For Build-Measure-Learn, see lean-startup. For usability audits, see ux-heuristics. 5-6 — hypotheses exist but criteria are vague or fidelity is over-invested; design and research still partly siloed. <=3 — heavy deliverables, untested assumptions, output-counting, no experiment log.

Q: What does lean-ux require?

| Roadmap planning | Rank features by assumption risk | Prioritize features whose success depends on untested beliefs |

Q: How do I install lean-ux?

Run: npx -y skills add https://github.com/wondelai/skills --skill lean-ux --agent claude-code — the source lives at github.com/wondelai/skills.

What it does

5-6 — hypotheses exist but criteria are vague or fidelity is over-invested; design and research still partly siloed.

<=3 — heavy deliverables, untested assumptions, output-counting, no experiment log.

Prioritize on two axes: risk (how damaging if wrong) and uncertainty (how little we know)

Test high-risk, high-uncertainty assumptions first

Write assumptions collaboratively as a team, not in isolation

Standard format: "We believe [outcome] will happen if [persona] achieves [action] with [feature]"

Every hypothesis specifies persona, action, outcome, and measurable signal

lean ux

Source

Repository: https://github.com/wondelai/skills

lean-ux FAQ

What does the lean-ux skill do?

Apply lean thinking to UX: hypothesis-driven design, collaborative sketching, and rapid experiments instead of heavy deliverables. Use when the user mentions "Lean UX", "design hypothesis", "outcome over output", "design studio method", "assumption mapping", "lightweight research", "too much design documentation", or "get the team designing together". Also trigger when reducing design-documentation overhead, getting cross-functional teams to co-design, or running fast usability experiments. Covers hypothesis statements, MVPs for UX, and cross-functional collaboration. For Build-Measure-Learn, see lean-startup. For usability audits, see ux-heuristics. 5-6 — hypotheses exist but criteria are vague or fidelity is over-invested; design and research still partly siloed. <=3 — heavy deliverables, untested assumptions, output-counting, no experiment log.

What does lean-ux require?

| Roadmap planning | Rank features by assumption risk | Prioritize features whose success depends on untested beliefs |

How do I install lean-ux?

Run: npx -y skills add https://github.com/wondelai/skills --skill lean-ux --agent claude-code — the source lives at github.com/wondelai/skills.

Maintain lean-ux?

Let people know it's listed here — add the badge (live metrics, light/dark aware) or a plain link to your README or docs.

[lean-ux on getagentictools](https://getagentictools.com/skills/wondelai-skills-lean-ux?ref=badge)

npx agentictools info skills/wondelai-skills-lean-ux

The second line is the CLI lookup for this page — handy in READMEs and docs.