# Nw Leanux Methodology

LeanUX backlog management methodology - user story template, story sizing, story...

- Repository: https://github.com/nWave-ai/nWave (628 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-09-16
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add nWave-ai/nWave --skill nw-leanux-methodology -g -a claude-code -y`
Codex: `npx skills add nWave-ai/nWave --skill nw-leanux-methodology -g -a codex -y`
Cursor: `npx skills add nWave-ai/nWave --skill nw-leanux-methodology -g -a cursor -y`
Gemini CLI: `npx skills add nWave-ai/nWave --skill nw-leanux-methodology -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add nWave-ai/nWave`

## Description

LeanUX backlog management methodology - user story template, story sizing, story states, task types, Definition of Ready/Done, anti-pattern detection and remediation

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# LeanUX Backlog Management Methodology

"A backlog is not a todo list. It's a collection of validated hypotheses waiting to become working software."

## Story States

| State | Meaning | Entry Criteria |
|-------|---------|----------------|
| Draft | Idea captured, not validated | Has problem statement |
| Ready | Validated, has UAT, ready to build | All DoR items complete |
| In Progress | Actively being built | UAT test written (RED) |
| In Review | Code complete, awaiting review | All tests green |
| Done | Merged, deployed, validated | UAT passes in production |
| Blocked | Cannot proceed | Blocker documented |

## Story Sizing Criteria

### Right-Sized
Completable in 1-3 days | 3-7 UAT scenarios | Delivers demonstrable value | Explainable in 2 minutes

### Oversized Indicators
>7 UAT scenarios | >3 days effort | Multiple distinct user outcomes | Cannot demonstrate in single session

### Splitting Strategy
Split by user outcome, not technical layer. Each resulting story delivers independently demonstrable value.

Example: "User Management" (20 scenarios) splits into:
- "Quick Login" (5 scenarios) -- returning customer on trusted device
- "New Registration" (4 scenarios) -- first-time customer sign-up
- "Password Recovery" (3 scenarios) -- customer who forgot credentials
- "Profile Settings" (4 scenarios) -- customer updating preferences

## Definition of Ready (DoR) - Hard Gate

Stories pass ALL 8 items before proceeding to DESIGN wave.

### Checklist with Pass/Fail Examples

**1. Problem statement clear and in domain language**
- Pass: "Maria wastes 30 seconds typing credentials on every visit"
- Fail: "Users need authentication"

**2. User/persona identified with specific characteristics**
- Pass: "Returning customer (2+ orders) on trusted personal device"
- Fail: "User" or "Customer"

**3. At least 3 domain examples with real data**
- Pass: "Maria on her MacBook, last login 5 days ago, goes directly to dashboard"
- Fail: "User logs in successfully"

The rest: https://github.com/nWave-ai/nWave/blob/HEAD/nWave/skills/nw-leanux-methodology/SKILL.md