acceptance-criteria-writer

Draft measurable acceptance criteria using Robertson's Fit Criteria.

19|3|Updated Feb 28, 2026

Search Tags:#testing #requirements #validation #agile #quality-assurance #user-stories #acceptance-criteria

Ready to run

npx skills add https://github.com/qa-aman/claude-skills --skill acceptance-criteria-writer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: acceptance-criteria-writer
Source: https://github.com/qa-aman/claude-skills/tree/main/skills/by-role/business-analyst/acceptance-criteria-writer
Command: npx skills add https://github.com/qa-aman/claude-skills --skill acceptance-criteria-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Requirements and user stories often lack precise, testable acceptance criteria, leading to misinterpretations and late validation.

Core Features & Use Cases

Formal criterion drafting: Create measurable fit criteria using Robertson's framework to clearly define success.
Multi-path coverage: Ensure happy path, edge cases, error paths, and empty states are defined for robustness.
Testability alignment: Attach explicit verification methods and test types to each criterion so teams can validate implementations.
Use Case: For a user login flow, convert the story into measurable criteria like successful login, handling invalid credentials, and response times under load.

Quick Start

Draft acceptance criteria for a given requirement by applying Robertson's Fit Criteria and provide measurable verification steps.

Frequently Asked Questions about acceptance-criteria-writer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I write measurable acceptance criteria for agile user stories?▼

Acceptance criteria for agile user stories are defined by applying Robertson's Fit Criteria to establish measurable success thresholds, ensuring each requirement includes explicit verification methods for happy-path, edge, and error scenarios.

What should be included in acceptance criteria to cover edge cases and error paths?▼

Acceptance criteria should include multi-path coverage that explicitly defines happy path, edge cases, error paths, and empty states, attaching specific verification methods and test types to each scenario for robust validation.

Can I use Robertson's Fit Criteria to make requirements testable for QA workflows?▼

Yes, Robertson's Fit Criteria can be used to make requirements testable for QA workflows by formalizing measurable fit criteria, attaching explicit verification methods and test types to validate implementations across product and engineering scenarios.

How do you define verification methods for user story acceptance criteria?▼

Verification methods for user story acceptance criteria are defined by attaching explicit test types and measurement steps to each criterion, ensuring teams can validate implementations against multi-path scenarios like handling invalid credentials or response times under load.

When do I need to formalize acceptance criteria for a requirements workflow?▼

You need to formalize acceptance criteria for a requirements workflow when user stories lack precise, testable conditions, leading to misinterpretations and late validation across product, engineering, and QA teams during development.