requirements-format

Format feature specifications by enforcing standardized sections like Overview, Goals, Acceptance Criteria, and optional Tech Notes. This ensures agents receive complete, unambiguous requirements instead of making assumptions during implementation.

Agents implement incomplete requirements when specifications lack structure. Using a standardized feature format prevents out-of-scope bonus implementations and alerts you when Tech Notes contradict project rules before planning begins.

The best way to clarify business requirements is grouping business, technical, and scope questions into a structured workflow that waits for your answers before planning. This prevents assumptions during feature drafting.

You need a standardized specification format during brainstorming, feature drafting, and clarification phases. It validates specification sections and requires agents to read existing feature documents before requesting business clarifications.

Yes, you can validate existing feature docs by requiring the agent to read .docs/features/*/feature.md files. It checks for complete overviews, goals, acceptance criteria, and flags contradicting Tech Notes against project rules.