acceptance-criteria

Name: acceptance-criteria
Availability: InStock
Author: Scute

Define and refine acceptance criteria from requirements via persona identification and workflow mapping.

3|Updated Mar 4, 2026

Search Tags:#workflow #requirements #validation #personas #acceptance criteria #feature definition

Ready to run

npx skills add https://github.com/scute-sh/scute --skill acceptance-criteria-scute-sh

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: acceptance-criteria
Source: https://github.com/scute-sh/scute/tree/main/.claude/skills/acceptance-criteria
Command: npx skills add https://github.com/scute-sh/scute --skill acceptance-criteria-scute-sh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps ensure that software features meet user needs by clearly defining and validating acceptance criteria before development begins, preventing scope creep and misaligned expectations.

Core Features & Use Cases

Requirement Refinement: Clarifies ambiguous requirements by identifying key personas and their workflows.
Acceptance Criteria Generation: Writes specific, testable criteria for feature completion.
Use Case: Before building a new user profile editing feature, use this Skill to define who the users are (e.g., administrators, end-users), map out their editing workflows, and generate criteria like "End-users must be able to update their profile picture" and "Administrators must be able to reset any user's password."

Quick Start

Use the acceptance-criteria skill to define the acceptance criteria for a new user authentication feature.

Frequently Asked Questions about acceptance-criteria

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

FAQPage Schema

How do I write testable acceptance criteria for software features?▼

To write testable acceptance criteria, you must analyze requirements by identifying key personas and mapping their workflows. This process clarifies ambiguous project scope and generates specific criteria from user perspectives before development begins.

What is the best way to define a clear definition of done before coding?▼

Defining a clear definition of done requires refining feature requirements through persona identification and workflow mapping. This approach establishes testable criteria for feature completion, preventing scope creep and misaligned expectations.

How do I clarify ambiguous project scope and requirements?▼

Clarifying ambiguous project scope involves identifying key personas and mapping their specific workflows. By analyzing requirements through user perspectives, you can establish clear boundaries and generate structured validation criteria for development.

Can I use persona identification to prevent scope creep in feature development?▼

Persona identification prevents scope creep by validating acceptance criteria against specific user workflows before coding begins. Mapping user roles like administrators and end-users ensures features meet actual needs without expanding requirements.

How do acceptance criteria map to user workflows and personas?▼

Acceptance criteria map to user workflows by analyzing how specific personas interact with a feature. Identifying roles like end-users or administrators allows you to generate targeted criteria, such as updating profile pictures or resetting passwords, based on their workflows.

What format does generated acceptance criteria need to follow?▼

Generated acceptance criteria require structured output in Markdown format for review and validation. This structured approach ensures testable criteria are clearly documented and aligned with user perspectives before development begins.