acceptance-criteria-define

To define acceptance criteria, provide a feature description or plan file. The skill derives proposed criteria covering functional correctness, validation, and non-functional requirements, then confirms them with you for review and modification.

Writing testable requirements prevents scope creep by formalizing what 'done' looks like. This skill generates a checklist of requirements from your context, ensuring features have well-defined, unambiguous validation standards before development proceeds.

You can generate an acceptance criteria checklist by feeding an existing plan file into the skill. It automatically derives proposed criteria, allows you to confirm and modify them, and saves the final output to `acceptance_criteria.md`.

Yes, you can review and modify generated acceptance criteria. The skill presents proposed criteria derived from your feature definition for explicit user confirmation before writing the finalized standards to a plan file or dedicated markdown document.

Defining acceptance criteria supports error handling, integration, and validation requirements. The skill ensures these non-functional aspects are explicitly included alongside functional correctness checks when formalizing feature standards.

Finalized acceptance criteria are saved to a plan file or a dedicated `acceptance_criteria.md` document. This standardized output ensures the validated feature requirements are persistently documented for development and testing reference.