propose-feature-requirements

EARS notation structures functional requirements using specific keywords to define conditions and system responses. This skill guides you through drafting these structured requirement statements, ensuring precise and unambiguous specifications for your feature concepts.

Drafting a feature specification involves copying a unified template and populating overview, functional, non-functional, and appendix sections. This skill enforces a guided workflow to transform an approved concept into a complete, structured requirements document.

Yes, generating non-functional requirements alongside functional ones is supported. The skill provides a structured template to specify both categories using EARS keywords, ensuring comprehensive coverage of system constraints and behaviors within the same document.

Structuring a requirements document requires defining a short ID prefix, populating an overview, specifying functional and non-functional requirements with EARS keywords, and organizing appendices. This skill automates that formatting to yield a consistent feature specification.

Yes, an approved feature concept is a prerequisite. The skill's workflow begins with concept verification and idea-honing checks to ensure the foundational idea is solid before proceeding to template copying and structured requirement drafting.

Using EARS notation for feature requirements eliminates ambiguity found in plain text by enforcing keyword-driven syntax for conditions and responses. This skill applies that structured process to produce precise, testable specifications.