acceptance-criteria-drafter

You can draft acceptance criteria by engaging in a structured interview process that collects feature goals, actors, and success criteria, then generates a structured Markdown draft saved in the .tmp folder for team review.

Generating testable requirements for GitHub Issues is best handled by an interview-driven approach that elicits user goals and constraints, producing a concise Markdown draft focused on verifiable conditions.

Yes, you can use an interview process to capture edge cases and non-functional requirements, as the structured questioning specifically targets optional constraints to ensure comprehensive acceptance criteria.

You can save acceptance criteria drafts as Markdown files by completing the interview process, which outputs a structured file named ac-draft-YYYYMMDD-N.md directly into the .tmp folder for immediate review and iterative refinement.

Yes, the acceptance criteria drafting process supports iterative refinement by allowing you to answer clarifying questions repeatedly and regenerate the Markdown draft until the criteria meet your approval.

You need a Markdown format for acceptance criteria to ensure verifiability, as the drafting process focuses on producing concise, testable conditions that clearly define user goals and success metrics.