Skill

requirements-engineering

Requirements engineering: INVEST criteria for user stories, Given-When-Then acceptance criteria with edge cases, MoSCoW prioritization, vertical slices, story mapping, decomposition patterns, non-functional requirements, Definition of Done. Use when writing user stories, breaking down epics, defining acceptance criteria.

Install

npx claudepluginhub rnavarych/alpha-engineer --plugin billy-milligan

Tool Access

This skill is limited to using the following tools:

ReadGrepGlob

Preview

- Writing user stories that meet INVEST criteria

Supporting Assets

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.md

SKILL.md

Similar Skills

agent-harness-construction

Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.

everything-claude-code

156.2k

accessibility

Designs, implements, and audits WCAG 2.2 AA accessible UIs for Web (ARIA/HTML5), iOS (SwiftUI traits), and Android (Compose semantics). Audits code for compliance gaps.

everything-claude-code

156.2k

agent-eval

Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.

everything-claude-code

156.2k

Stats

Parent Repo Stars9

Parent Repo Forks0

Last CommitFeb 23, 2026

Actions

View Source View Plugin View on GitHub View README

requirements-engineering

Core principles

INVEST for user stories — Independent, Negotiable, Valuable, Estimable, Small, Testable

GWT for acceptance criteria — Given-When-Then; no "and" chains (split them)

Vertical slices — each story delivers value end-to-end, not "backend only"

Edge cases in the story — not as surprises during implementation

Non-functional requirements are requirements — performance, accessibility, security belong in stories

References available

references/user-story-patterns.md — INVEST checklist, story format templates, story mapping

references/story-splitting.md — splitting strategies by workflow step, data variation, CRUD, quality tier

references/acceptance-criteria.md — Given-When-Then structure, rules per clause, happy path example

references/boundary-conditions.md — boundary condition discovery checklist, negative and concurrent scenario examples

references/definition-of-done.md — DoD concept, recommended DoD checklist

references/moscow-prioritization.md — MoSCoW category definitions, 60/20/20 rule, e-commerce example

references/mvp-definition.md — hypothesis-first approach, MVP scope decision table, Wizard of Oz test

references/scope-creep.md — warning signals, response protocol, negotiation script, release scope lock

references/scope-management.md — story points Fibonacci scale, Planning Poker rules, velocity and capacity formula

Requirements Engineering

When to use

Writing user stories that meet INVEST criteria
Defining complete acceptance criteria with edge cases
Breaking down large features into vertical slices
Prioritizing backlog with MoSCoW
Defining non-functional requirements for a feature

Core principles

INVEST for user stories — Independent, Negotiable, Valuable, Estimable, Small, Testable
GWT for acceptance criteria — Given-When-Then; no "and" chains (split them)
Vertical slices — each story delivers value end-to-end, not "backend only"
Edge cases in the story — not as surprises during implementation
Non-functional requirements are requirements — performance, accessibility, security belong in stories

References available

references/user-story-patterns.md — INVEST checklist, story format templates, story mapping
references/story-splitting.md — splitting strategies by workflow step, data variation, CRUD, quality tier
references/acceptance-criteria.md — Given-When-Then structure, rules per clause, happy path example
references/boundary-conditions.md — boundary condition discovery checklist, negative and concurrent scenario examples
references/definition-of-done.md — DoD concept, recommended DoD checklist
references/moscow-prioritization.md — MoSCoW category definitions, 60/20/20 rule, e-commerce example
references/mvp-definition.md — hypothesis-first approach, MVP scope decision table, Wizard of Oz test
references/scope-creep.md — warning signals, response protocol, negotiation script, release scope lock
references/scope-management.md — story points Fibonacci scale, Planning Poker rules, velocity and capacity formula

Assets available

assets/requirements-template.md — ready-to-fill story + AC template for new features