requirements

Capture and organize feature requirements using EARS notation.

Updated May 9, 2020

Search Tags:#planning #specification #requirements #EARS #domain-model #pre-design

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-implementation thinking tool for complex features. Produces disposable requirements artifacts — specs are thinking tools, not sources of truth. Once implemented, the code absorbs and replaces them.

Core Features & Use Cases

EARS-based requirement patterns to clarify scope, edge cases, and open questions.
Scope boundary guidance for what to build vs how to plan, plus pre-design and domain decisions references.
Templates for acceptance criteria, entity sketches, edge cases, and open questions to validate the approach before implementation.

Quick Start

Provide a feature concept and run this skill to generate a structured requirements artifact for review.

Frequently Asked Questions about requirements

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

FAQPage Schema

How do I write structured requirements for complex software features?▼

Pre-implementation requirements planning uses the EARS notation to capture scope, acceptance criteria, edge cases, and open questions. This approach clarifies domain concepts and entities before any implementation begins.

What is the EARS notation for software specification?▼

The EARS notation is a structured requirement pattern used for software specification to define conditions and system responses. It guides pre-implementation planning by structuring acceptance criteria, edge cases, and open questions.

When do I need to create a pre-design specification for a feature?▼

You need a pre-design specification when a feature involves new entities, multiple endpoints, or complex domain concepts. Creating a disposable artifact validates the approach through entity sketches and decision questions before coding starts.

How do I define scope boundaries for feature planning?▼

Define scope boundaries for feature planning by separating what to build from how to plan. Using EARS-based requirement patterns captures these boundaries alongside pre-design decisions and domain model sketches.

What should be included in a pre-implementation requirements artifact?▼

A pre-implementation requirements artifact should include acceptance criteria, entity sketches, edge cases, and open decision questions. These components ensure domain concepts and scope boundaries are validated before coding begins.

Are feature specification artifacts meant to be maintained after implementation?▼

Feature specification artifacts are disposable thinking tools, not long-term sources of truth. Once the feature is implemented, the codebase absorbs and entirely replaces the pre-implementation requirements document.