ears-acceptance-criteria

What problem does it solve?

This Skill simplifies the process of writing clear, testable acceptance criteria using EARS notation, helping developers define the exact behaviors a system should exhibit.

Core Features & Use Cases

• EARS Syntax Support: Utilizes EARS (Easy Approach to Requirements Syntax) for creating unambiguous, testable requirements.
• Atomic Behaviors: Ensures each criterion states a single, observable behavior.
• Pattern Recognition: Identifies five key patterns: ubiquitous, event-driven, state-driven, unwanted-behavior, and optional feature.
• Use Case: Ideal for authoring requirements documents, turning vague requests into actionable criteria, or defining task completion standards.

Quick Start

Create an acceptance criterion for the "Login" feature with the command: aim task create --ac "WHEN valid credentials are submitted THE SYSTEM SHALL authenticate the user."