Generate requirement definition documents using EARS notation.
npx skills add https://github.com/Foo-x/dotfiles --skill rdd
Please help me install this Agent Skill. Skill: rdd Source: https://github.com/Foo-x/dotfiles/tree/main/claude/skills/rdd Command: npx skills add https://github.com/Foo-x/dotfiles --skill rdd
This Skill streamlines the creation of clear, verifiable requirement documents using the EARS (Easy Approach to Requirements Syntax) notation, ensuring all functional and non-functional aspects are captured without delving into implementation details.
Use the rdd skill to create a requirements document for the new user authentication feature.
High-intent search queries and answers about installing and using this skill.
EARS notation requirement documents are generated through interactive clarification to define new features, capturing functional and non-functional aspects while excluding implementation details. The output structure formats requirements into Ubiquitous, Event-driven, State-driven, Optional, and Unwanted categories.
Defining acceptance criteria and edge cases for product specifications is achieved by engaging in an interactive dialogue that clarifies needs. This process ensures all verifiable requirement aspects are captured and produces a formal document ready for the development team.
Yes, modifying existing software requirements is fully supported. The interactive clarification process handles requirement definition for both new feature launches and modifications, ensuring clarity on updated acceptance criteria and edge cases.
Interactive clarification for EARS specifications works by engaging you in a dialogue to extract needs and edge cases. It utilizes reference materials for EARS patterns and a structured template to ensure the final requirement definition document is clear and verifiable.
No prior knowledge of EARS patterns is needed to generate software development requirements. The process utilizes internal reference materials for EARS patterns to guide the interactive clarification and format the structured output automatically.
You should avoid using EARS notation when your goal is to delve into implementation details rather than capturing functional aspects. This approach focuses strictly on creating clear, verifiable requirement documents without specifying how the feature should be built.
nilecuiTransform initial concepts into detailed design specifications through structured questioning.
JohannesKoningsConvert project plans and PRDs into structured issue tracker tickets.
xxyjGenerate EARS-formatted specification documents for AI model changes.
UserAdConvert informal user stories into formal, testable EARS requirements.
