verify-acceptance-criterialisted

Verify acceptance criteria quality and identify gaps. Use this skill whenever you need to evaluate acceptance criteria (ACs) to ensure they meet quality standards. Trigger on: "review these ACs", "check if these acceptance criteria are good", "validate my user story criteria", "improve our acceptance criteria", "audit these requirements", "do these ACs pass review", or similar requests. Also use proactively when someone shares acceptance criteria that look hastily written or vague. The skill analyzes criteria against five key dimensions (clarity, testability, outcome-focus, measurability, independence), scores issues by severity (critical/major/minor), and generates a structured report. It can also rewrite poor criteria into better ones or convert them to user story format.
felipecabargas/gambit · ★ 2 · Code & Development · score 74

Install: claude install-skill felipecabargas/gambit

# Acceptance Criteria Verifier ## When to Use Use this skill to evaluate acceptance criteria quality. It's most valuable when: - Reviewing criteria before development starts (catch issues early) - Auditing existing criteria that have caused confusion or rework - Ensuring criteria align with product standards - Converting vague requirements into precise, testable statements - Preparing criteria for team handoff to engineering ## Input Format The skill accepts acceptance criteria in multiple formats: - **Plain text**: A list pasted directly into the message - **Markdown**: Bullet points or numbered lists - **CSV/Excel**: Uploaded spreadsheet files - **JSON**: Structured data - **Mixed**: Any combination of the above Example inputs: ``` Given the user is logged in When they navigate to the dashboard Then they should see a list of their recent items ``` Or: ``` - Display loads within 2 seconds - All product images render correctly - User can filter by category ``` ## Evaluation Framework Each acceptance criterion is evaluated against **five dimensions of quality**: ### 1. Clarity & Conciseness - Is the language plain and unambiguous? - Can all stakeholders interpret it the same way? - Is it free of jargon or unexplained terms? - Does it say exactly one thing, clearly? **Critical Issues**: Ambiguous terms with multiple interpretations **Major Issues**: Vague language; jargon without definition **Minor Issues**: Wordy phrasing that could be tightened ### 2. Testabili