Menu
Improve acceptance criteria so they are testable, unambiguous, and complete.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Safely sync a branch with origin/main using fetch + rebase, with an optional "accept current" conflict policy.
Add an MCP integration section (tools, auth, error handling, observability, tests) to an existing spec.
Extract MUST/SHOULD/MAY requirements, constraints, flows, and open questions from long epic/PRD text (PDF/TXT export).
Identify edge cases, security/privacy issues, operational risks, and delivery risks in a spec.
Propose a safe rollout/migration plan with monitoring and rollback steps.
Produce a clear, review-ready SDD specification skeleton in Markdown.
| name | ac-quality-check |
| description | Improve acceptance criteria so they are testable, unambiguous, and complete. |
Upgrade acceptance criteria (AC) so they are verifiable, unambiguous, and complete.
Review the following acceptance criteria and improve them.
Rules:
- Each AC must be testable/verifiable (avoid vague words like “fast”, “nice”, “robust”).
- Prefer measurable thresholds (latency, size, limits) when relevant.
- Include negative cases (invalid input, permissions, missing data).
- Separate concerns: one requirement per bullet.
- If an AC implies a behavior change, include compatibility expectations.
Output:
1) Revised AC list
2) A short note listing what was unclear/missing