specification-writing

Testable acceptance criteria are measurable conditions that a feature must satisfy. This Skill writes precise specifications using MUST and MUST NOT language to ensure requirements are verifiable and unambiguous.

To write precise specifications, provide a concise feature request with a problem statement, user journeys, and measurable acceptance criteria. The Skill then structures these into clear functional and non-functional requirements.

Defining system boundaries and user journeys involves capturing the problem statement and mapping user interactions. This Skill structures those inputs to enforce clear scope and testable requirements across product teams.

Yes, you can include non-functional requirements with measurable criteria. The Skill provides dedicated templates for both functional and non-functional requirements to ensure consistency and testability.

Yes, this approach works for complex feature requests by breaking them down into problem statements, user journeys, system boundaries, and acceptance criteria to guide teams with precise, testable requirements.

Product teams should use MUST and MUST NOT language to eliminate ambiguity in specifications. This Skill enforces this language structure to ensure requirements are strict, testable, and consistently understood.