lean-ux

Malicious tool definition detected

Tool: SKILL.md [1/3] Description: --- name: lean-ux description: '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", "UX experiment", "collaborative design", or "outcome over output".

Malicious tool definition detected

Tool: references/agile-integration.md [1/3] Description: # Agile Integration for Lean UX Lean UX was designed to work inside Agile development teams, not alongside them.

Tool: references/agile-integration.md [2/3] Description: experiment | Data meets pre-set success threshold | Ready for delivery sprint planning | | **Invalidated** | Hypotheses disproven by experiment | Data falls below pre-set threshold | Archived with learnings; team decides pivot or drop | | **Delivery** | Validated designs in development | Enters delivery sprint | Shipped to production | ### Backlog Grooming for Lean UX During backlog grooming: 1.

Tool: references/agile-integration.md [3/3]

Malicious tool definition detected

Tool: references/case-studies.md [1/3] Description: # Case Studies: Lean UX in Practice These case studies illustrate how Lean UX principles apply across different organizational contexts. Each scenario is a realistic composite based on common patterns, not a specific company. The goal is to show how hypothesis-driven design, collaborative practices, and outcome-focused metrics work in the real world.

Tool: references/case-studies.md [2/3] Description: sync):** Wizard of Oz test. Offered 10 users "automatic bank sync" and manually categorized their transactions for 1 week.

Malicious tool definition detected

Tool: references/collaborative-design.md [2/3] Description: wireframe decks, annotated mockups with 200 footnotes, user flow diagrams that are outdated by the time they are printed. Lean UX reduces deliverables to the minimum needed for shared understanding.

Tool: references/collaborative-design.md [3/3]

Malicious tool definition detected

Tool: references/experiment-patterns.md [1/3] Description: # Experiment Patterns for Lean UX Experiments are the engine of learning in Lean UX. The right experiment answers the hypothesis with the least effort. Choosing the wrong experiment type wastes time, money, or both. This reference covers the full spectrum of UX experiments, from napkin sketches to coded A/B tests.

Tool: references/experiment-patterns.md [2/3] Description: traffic to reach statistical significance - The hypothesis involves a measurable behavior change in an existing product - You need high-confidence evidence to justify a significant investment **When NOT to use:** - Traffic is too low for statistical significance (fewer than 1,000 users per variant) - The concept is entirely new (test with prototypes first) - The change is too small to produce a detectable effect ## Choosing the Right Exp

Tool: references/experiment-patterns.md [3/3] Description: experiments: | If you need to learn...

Malicious tool definition detected

Tool: references/hypothesis-canvas.md [1/2] Description: # Hypothesis Canvas The hypothesis canvas is the central planning artifact in Lean UX.

Tool: references/hypothesis-canvas.md [2/2] Description: reports with our auto-generated template feature save at least 2 hours per week.

Malicious tool definition detected

Tool: references/outcome-metrics.md [1/3] Description: # Outcome Metrics for Lean UX Lean UX shifts the definition of success from "did we ship it?" to "did it change behavior?" This reference covers how to choose, define, and track metrics that measure real outcomes rather than outputs.

Tool: references/outcome-metrics.md [2/3] Description: framework that aligns well with Lean UX because Key Results are outcome-based, not output-based.

Tool: references/outcome-metrics.md [3/3]