Stats
Actions
Tags
From billy-milligan
Guides requirements engineering with INVEST user stories, Given-When-Then acceptance criteria including edge cases, MoSCoW prioritization, vertical slices, story mapping, decomposition patterns, non-functional requirements, and Definition of Done. Use for writing stories, epic breakdowns, and backlog prioritization.
How this skill is triggered — by the user, by Claude, or both
Slash command
/billy-milligan:requirements-engineeringThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
- Writing user stories that meet INVEST criteria
assets/requirements-template.mdreferences/acceptance-criteria.mdreferences/boundary-conditions.mdreferences/definition-of-done.mdreferences/moscow-prioritization.mdreferences/mvp-definition.mdreferences/scope-creep.mdreferences/scope-management.mdreferences/story-splitting.mdreferences/user-story-patterns.mdreferences/user-story-patterns.md — INVEST checklist, story format templates, story mappingreferences/story-splitting.md — splitting strategies by workflow step, data variation, CRUD, quality tierreferences/acceptance-criteria.md — Given-When-Then structure, rules per clause, happy path examplereferences/boundary-conditions.md — boundary condition discovery checklist, negative and concurrent scenario examplesreferences/definition-of-done.md — DoD concept, recommended DoD checklistreferences/moscow-prioritization.md — MoSCoW category definitions, 60/20/20 rule, e-commerce examplereferences/mvp-definition.md — hypothesis-first approach, MVP scope decision table, Wizard of Oz testreferences/scope-creep.md — warning signals, response protocol, negotiation script, release scope lockreferences/scope-management.md — story points Fibonacci scale, Planning Poker rules, velocity and capacity formulaassets/requirements-template.md — ready-to-fill story + AC template for new featuresnpx claudepluginhub rnavarych/alpha-engineer --plugin billy-milliganWrites user stories and acceptance criteria using INVEST principles and Given/When/Then format. Helps teams scope, split, and review backlog items before sprint planning.
Decomposes features into granular, INVEST-compliant user stories with acceptance criteria, MoSCoW priorities, and relative estimates (S/M/L). Useful for breaking down requirements into 8-hour implementable units.
Generates prioritized user stories with Given/When/Then acceptance scenarios from feature descriptions. Ensures independent testability, clear value, and P1-P3 prioritization.