spec-requirements

To generate a requirements.md file using EARS notation, provide a context.json file or manual user input. It parses the context, asks clarifying questions if needed, and outputs structured user stories and functional requirements.

EARS (Easy Approach to Requirements Syntax) is a structured syntax for writing clear, consistent requirement statements. It enforces specific sentence structures that reduce ambiguity in functional requirements, making generated documentation easier to verify and implement.

Yes, you can define product requirements interactively without a pre-existing context file by providing manual user input. The Skill supports interactive clarification and JSON answer injection to define requirements on the fly.

Yes, the requirements generation process includes feasibility verification. Along with creating user stories and EARS-compliant functional requirements, the Skill performs automated feasibility checks to validate the defined requirements.

To pass bug fix context for functional requirements generation, structure your details in a context.json file, such as within a docs/bugs/issue-name/ directory. The Skill parses this JSON context to draft the relevant requirements.md file.

The best way to transition from generated requirements to software design is to refine the outputted requirements.md file and pass it to the /spec-design Skill, which handles the downstream design process based on the structured EARS requirements.