Capture and organize feature requirements using EARS notation.
npx skills add https://github.com/Fenntasy/dotfiles --skill requirements-fenntasy
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
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.
Provide a feature concept and run this skill to generate a structured requirements artifact for review.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
heymishyCompare current benefit metrics against baselines and update metric artefacts.
tgautierGenerate EARS requirements with acceptance criteria and edge cases.
psmonGenerate technical diagrams and design sketches in .pen format using Pencil MCP.
LucaDeLeoDecompose natural-language project goals into epics and user stories with acceptance criteria.
