requirements

Generate EARS requirements with acceptance criteria and edge cases.

2|1|Updated Jun 30, 2019

Search Tags:#requirements #edge-cases #ears #acceptance-criteria #feature-planning #entity-sketches #pre-design

Ready to run

npx skills add https://github.com/tgautier/dotfiles --skill requirements-tgautier

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requirements
Source: https://github.com/tgautier/dotfiles/tree/main/claude/skills/requirements
Command: npx skills add https://github.com/tgautier/dotfiles --skill requirements-tgautier

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-implementation elicitation using EARS notation to generate disposable requirements artifacts and boundary definitions for complex features.

Core Features & Use Cases

Produces acceptance criteria, edge cases, entity sketches, and open questions to guide implementation.
Applies to features with new domains, multiple endpoints, or evolving domain concepts requiring precise scope.
Supports structured planning and decision records that can be translated into PRs or tickets.

Quick Start

Provide a brief prompt to generate a complete requirements artifact for a new feature in terms of EARS patterns.

Frequently Asked Questions about requirements

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

FAQPage Schema

What is EARS notation for writing software requirements?▼

EARS notation is a structured syntax for writing precise, testable requirements. It clarifies complex features by generating acceptance criteria, edge cases, and boundary definitions to guide implementation.

How do I write acceptance criteria for complex features with multiple endpoints?▼

Write acceptance criteria for complex features using EARS notation to produce testable requirements. This approach generates boundary definitions, entity sketches, and open questions for evolving domain concepts.

When do I need to use EARS notation for feature planning?▼

You need EARS notation for feature planning when working with new domain entities, multi-endpoint features, or evolving domain concepts. It produces disposable requirements artifacts that define precise scope boundaries.

Can I use EARS requirements to generate entity sketches and edge cases?▼

Yes, EARS requirements generate entity sketches and edge cases alongside acceptance criteria and open questions. These outputs inform pre-design planning and create structured decision records for implementation.

What's the best way to define scope boundaries for evolving domain concepts?▼

The best way to define scope boundaries for evolving domain concepts is pre-implementation elicitation using EARS notation. This produces structured boundary definitions and testable requirements for feature planning.

Does EARS specification work for pre-implementation feature planning?▼

Yes, EARS specifications work effectively for pre-implementation feature planning by producing disposable requirements artifacts. These artifacts translate into structured decision records, PRs, or implementation tickets.