
Requirements Engineering
This one walks you through turning fuzzy feature requests into concrete, testable requirements using the EARS format (Easy Approach to Requirements Syntax). You get patterns like "WHEN user uploads file over 10MB THEN system SHALL display error" instead of vague stuff like "uploads should work well." It covers the full loop: capture user stories, write acceptance criteria, identify edge cases, validate completeness. The examples are solid, real-world scenarios like file uploads and search features. Use it at the start of any project when stakeholders are hand-waving about what they want. It won't make requirements gathering fun, but it'll keep you from building the wrong thing.
- skills.sh installs
- 355
- GitHub stars
- 757
- last updated
- Aug 21, 2026
Install
$ npx -y skills add jasonkneen/kiro --skill requirements-engineering --agent claude-codeInstalls into .claude/skills of the current project.
Files
Requirements Engineering
Master the art of capturing what needs to be built before diving into how to build it. This skill teaches the EARS (Easy Approach to Requirements Syntax) format for creating clear, testable requirements.
When to Use This Skill
Use requirements engineering when:
- Starting any new feature or project
- Clarifying ambiguous stakeholder requests
- Creating acceptance criteria for user stories
- Documenting system behavior for testing
- Ensuring all team members share understanding
The EARS Format
EARS provides consistent patterns for writing requirements that are specific, testable, and unambiguous.
Basic Patterns
Event-Response (Most Common):
WHEN [triggering event] THEN [system] SHALL [required response]
Conditional Behavior:
IF [precondition is met] THEN [system] SHALL [required response]
Complex Conditions:
WHEN [event] AND [additional condition] THEN [system] SHALL [response]
Optional Conditions:
WHEN [event] OR [alternative event] THEN [system] SHALL [response]
Advanced Patterns
State-Based:
WHEN [system is in specific state] THEN [system] SHALL [behavior]
Sponsors
Details
- Repository
- github.com/jasonkneen/kiro
- Categories
- Backend & APIs, Code Review & Quality, Design & UI/UX
- First seen
- Jun 3, 2026