← ClaudeAtlas

lh-backloglisted

Turning validated problems into buildable work: user stories, acceptance criteria, prioritization, and roadmap. Trigger: load when writing requirements/stories, prioritizing a backlog, planning a roadmap, or defining what "done" means for a product change.
jrodrigopuca/local-agents · ★ 2 · AI & Automation · score 72
Install: claude install-skill jrodrigopuca/local-agents
## Critical Patterns ### 1. Write stories as intent + outcome, never as implementation A user story states WHO, WHAT they're trying to accomplish, and WHY — "as a returning customer, I want to find a past order quickly, so I can reorder without hunting". It does NOT say which component, which query, which layout — that's the team's to solve ([judgment #1](../../AGENTS.md)). The story is a promise to have a conversation, not a spec handed down. ### 2. Acceptance criteria make "done" testable and shared Every story carries acceptance criteria: the observable conditions that mean it's solved. Written as concrete, checkable statements ("returning user sees their last 10 orders sorted by date; tapping one pre-fills a reorder"), they become three things at once: the team's definition of done, the list [qa's `lh-test-design`](../../../qa/skills/lh-test-design/SKILL.md) derives coverage from, and the states [ux-ui's `lh-ux-flows`](../../../ux-ui/skills/lh-ux-flows/SKILL.md) must design (empty, error, overflow included — a story with only the happy-path criterion is a fifth of a story). Give them a shape the team can read the same way twice — Given / When / Then, or a table of examples — and include the criteria that are not features: the response time, the accessibility floor, the security floor. A story that omits those doesn't skip them; it ships them as surprises. Fuzzy criteria are where "done" becomes an argument. ### 3. Slice vertically — thin, valuable, shippable Break b