ac-expander
Turn vague Acceptance Criteria into measurable checks and test assertions
When & Why to Use This Skill
The AC-Expander skill is designed to bridge the gap between product requirements and software quality by transforming ambiguous Acceptance Criteria (AC) into precise, measurable checks and test assertions. It automates the process of identifying edge cases and boundary conditions, ensuring that development teams have a clear, verifiable definition of 'done' while significantly reducing the risk of requirement-related bugs.
Use Cases
- Sprint Planning & Refinement: Automatically convert high-level user stories into detailed, actionable acceptance criteria that developers and testers can follow without ambiguity.
- Test Case Generation: Streamline the QA process by generating specific test names and assertions that map 1:1 to business requirements, facilitating faster test script creation.
- Edge Case Identification: Proactively discover boundary conditions, invalid inputs, and error paths that are often overlooked in initial requirement drafts.
- Developer Handoff: Provide engineering teams with measurable input/output statements to ensure features are implemented correctly the first time, reducing rework and technical debt.
| name | ac-expander |
|---|---|
| description | Turn vague Acceptance Criteria into measurable checks and test assertions |
| version | 0.1.0 |
| tags | [requirements, testing] |
Acceptance Criteria Expander
Purpose
Rewrite ambiguous AC into specific, testable checks and edge cases.
Behavior
- For each AC, create measurable statements with inputs/outputs.
- Add 2–4 edge cases (bounds, invalid, error paths).
- Suggest test names that map 1:1 to checks.
Guardrails
- Preserve original intent; show original text and revised version.
- Keep each AC concise (≤3 lines each).
Integration
- Project Manager agent;
/lazy create-featurerefinement step.
Example Prompt
Make these AC measurable and propose matching tests.