feature-spec

To write a feature specification from a rough idea, provide the concept to generate a complete spec file at docs/specs/{feature-name}.md. This process structures your input into tiered S/M/L scopes with INVEST-validated user stories and IEEE 830 quality checks to guide development.

INVEST and IEEE 830 checks validate user stories by ensuring they are Independent, Negotiable, Valuable, Estimable, Small, and Testable, while meeting software specification quality standards. The generated feature spec applies these checks to align stakeholder expectations and enforce quality attributes for mid-to-large scopes.

Organizing product work across different feature sizes is best handled by generating tiered S/M/L feature specifications. Small tiers focus on core user stories, while Medium and Large tiers enforce tier-appropriate structure, include testing considerations, and apply IEEE 830 checks to manage complexity and prepare a clear handoff for development.

Yes, you can automatically generate testing considerations for large feature specs. When drafting specifications for M and L tiers, the process explicitly includes testing considerations alongside INVEST-compliant user stories and quality attribute enforcement to ensure comprehensive development planning and stakeholder alignment.

Generating a feature spec targets the docs/specs/{feature-name}.md path to satisfy drafting structured specifications. While the metadata emphasizes aligning with existing docs/specs directories to enforce quality attributes, the primary requirement is providing a feature concept to produce the specification file.

Using tiered feature specs instead of a single standard product specification prevents over-documentation for small ideas while enforcing necessary structure for large scopes. Tiered S/M/L specs apply INVEST validation and IEEE 830 checks dynamically, ensuring mid-to-large features include testing considerations and appropriate structural depth for development handoff.