Acceptance Criteria Builder

The problem

Vague requirements lead to scope creep and missed edge cases during development. Quality assurance often fails because acceptance criteria lack the specificity needed for automated or manual testing.

What it does

• Extracts testable criteria, edge cases, and negative tests from confirmed requirements.
• Separates facts from assumptions to prevent unconfirmed product decisions from leaking into the build.
• Maps out Happy Path, Error Path, permissions, and side effects for every feature.
• Performs cross-checks against existing test cases in tests/test-cases.md to ensure consistency.
• Generates a structured output with Given/When/Then scenarios, risk assessments, and required test data.

Why this beats prompting it yourself

Writing bulletproof acceptance criteria is tedious and prone to human oversight regarding edge cases. This skill enforces a strict verification logic that flags missing evidence as BLOCKED, preventing you from starting work on incomplete specs.

Use cases

• Transforming rough product notes into formal Given/When/Then acceptance criteria.
• Identifying technical risks and dependencies before a sprint planning session.
• Generating edge case test data requirements for QA teams.
• Reviewing existing requirements against internal test documentation for gaps.

Known limitations

Requires structured input including goals, roles, and risks to function effectively. Does not provide legal, medical, or financial advice.