story-writing

Testable acceptance criteria must be falsifiable statements that define a clear pass or fail condition. This Skill generates acceptance criteria using EARS forms like Ubiquitous, Event, State, Unwanted, and Optional, ensuring each criterion can be independently verified through a corresponding test stub.

Turning a feature idea into a user story requires packaging a value statement, falsifiable acceptance criteria, and failing-test stubs together. This Skill converts your concept into a ready-to-implement artifact, providing a single value statement and a test stub for each criterion to form a clear implementation contract.

A value statement summarizes the user need the feature addresses in one sentence. This Skill enforces a single well-formed value statement from your feature concept during discovery and planning, ensuring the requirement is focused before acceptance criteria and test stubs are generated.

EARS notation works for user stories by structuring acceptance criteria into unambiguous, testable forms. This Skill supports EARS forms including Ubiquitous, Event, State, Unwanted, and Optional, applying them to generate measurable requirements that can be independently implemented and verified.

Generating failing test stubs from acceptance criteria is the core output of this Skill. It produces a failing-test stub for each falsifiable acceptance criterion, establishing a testing contract that developers can use to verify implementation correctness.

Automated user story generation is not suitable for features lacking a clear value statement or when requirements are too vague to formulate falsifiable acceptance criteria. This Skill requires a one-sentence feature concept to produce a testable, ready-to-implement artifact.