Does it support non-functional requirements like performance?

Absolutely. The skill includes specific templates and workflows for defining performance, security, usability, and availability requirements in categorized markdown files.

What is EARS notation in the context of this skill?

EARS (Easy Approach to Requirements Syntax) is a template-based approach to writing requirements that reduces ambiguity. This skill uses it to create statements like 'When [Event], the system shall [Action]'.

Can I use this for existing projects?

Yes, the skill can be used to add new requirements to existing projects or to refactor current documentation into the EARS format for better clarity.

Where does the skill save the requirement files?

It creates a standardized directory structure at docs/requirements/, with subdirectories for user stories and non-functional requirements (NFRs).

Requirements Defining with EARS

Name: Requirements Defining with EARS
Author: windschord

bywindschord

•

Productivity & Workflow

Generates and manages structured, testable software requirement specifications using the EARS (Easy Approach to Requirements Syntax) framework.

The Requirements Defining skill streamlines the early stages of software development by transforming vague ideas into precise, testable documentation. Utilizing the EARS notation, it ensures that every requirement follows a logical syntax (Event, Condition, Action) to eliminate ambiguity. It automatically maintains a professional documentation structure within your repository, managing indices, detailed user stories, and categorized non-functional requirements like performance and security. This skill is ideal for teams needing high-quality specifications that bridge the gap between business needs and technical implementation.

Key Features

01Detailed user story generation with clear acceptance criteria

021 GitHub stars

03Automated documentation structure management for stories and NFRs

04Categorized non-functional requirement tracking (Performance, Security, Usability)

05Built-in verification checklists to ensure requirement quality and uniqueness

06EARS-compliant requirement syntax for maximum clarity and testability

Use Cases

01Initializing a new software project with a standardized requirement hierarchy

02Refining ambiguous stakeholder requests into actionable technical specifications

03Converting legacy documentation into structured, testable EARS-format requirements

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add windschord/claude_skils requirements-defining

For use in Claude.ai and ChatGPT

Key Features

01Detailed user story generation with clear acceptance criteria

021 GitHub stars

03Automated documentation structure management for stories and NFRs

04Categorized non-functional requirement tracking (Performance, Security, Usability)

05Built-in verification checklists to ensure requirement quality and uniqueness

06EARS-compliant requirement syntax for maximum clarity and testability

Use Cases

01Initializing a new software project with a standardized requirement hierarchy

02Refining ambiguous stakeholder requests into actionable technical specifications

03Converting legacy documentation into structured, testable EARS-format requirements