LeanUX backlog management methodology - user story template, story sizing, story states, task types, Definition of Ready/Done, anti-pattern detection and remediation
SkillScore95Maintained
On-demandOn-demand: invoked explicitly — never occupies your agent's context until called.
◆Product Management pack
Last verified 8/16/2026
What it changes
Passed 21 of 22 test cases with the skill, and 11 of 22 without it.
Without skill50%
With skill95%
Checks it passed that the model alone missed
Identifies the Generic Data anti-pattern
Identifies the anti-pattern as Implement-X
States that MoSCoW is assigned during Phase 2 (CRAFT)
and 8 more in the full report
10 fixed11 passed either way1 still failing0 broke
Pass-rate lift
+45 pp
Tokens
+84%
Agent turns
0%
Response time
-27%
Model gemini-3.6-flashMeasured 8/16/2026v121 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 10
Prompt
Developer Sam is ready to pick up story US-105 from the Ready state and begin development. What mandatory test prerequisite must Sam complete before moving US-105 to In Progress state?
What was checked, without and with the skill
Checked
Without skill
With skill
Specifies that a UAT test must be written in RED state before moving to In Progress
Missed
Passed
case-08 · gemini-3.6-flash · 8/16/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md202 linessingle file
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.