ears-spec-authoring

The EARS-lite approach structures acceptance criteria into five shapes covering ubiquitous, event-driven, state-driven, optional, and unwanted behavior to prevent vague requirements from slipping into tasks.

Convert tracker tickets into concrete acceptance criteria by assigning a stable AC-NNN ID to each condition and outcome, ensuring one AC per condition, and capturing unresolved decisions in a dedicated Open Questions section with Q-NNN IDs.

Handle open questions in a specification document by assigning an explicit Q-NNN ID to each unresolved decision within a dedicated Open Questions section, preventing vague requirements from slipping into development tasks.

Yes, you can apply EARS-lite to draft or edit an existing 01-spec.md file by selecting one of the five EARS shapes and assigning a stable AC-NNN ID to every condition and outcome to stabilize requirements.

You should avoid using EARS-lite when your acceptance criteria require detailed implementation instructions, as the format enforces single condition and outcome pairs with no implementation details to prevent scope creep.