acceptance-criteria-drafter

Name: acceptance-criteria-drafter
Availability: InStock
Author: Atman

Interview users to collect feature requirements and generate a Markdown Acceptance Criteria draft.

Updated Aug 23, 2026

Search Tags:#documentation #markdown #requirements #acceptance criteria #interview #draft #GitHub Issues

Ready to run

npx skills add https://github.com/atman-33/skills --skill acceptance-criteria-drafter

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: acceptance-criteria-drafter
Source: https://github.com/atman-33/skills/tree/main/skills/acceptance-criteria-drafter
Command: npx skills add https://github.com/atman-33/skills --skill acceptance-criteria-drafter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill reduces the time and ambiguity in defining Acceptance Criteria by guiding a structured interview process and generating a ready-to-use Markdown draft stored in the .tmp folder.

Core Features & Use Cases

Interview-driven AC drafting: collects feature goals, actors, and success criteria.
Markdown draft output: saves a .tmp/ac-draft-YYYYMMDD-N.md file for review and refinement.
Edge-case handling: captures optional constraints and non-functional requirements.
Use Case: When starting a new feature, run AC Drafter to produce a draft that product and dev teams can review.

Quick Start

Interact with the user to elicit feature requirements, then generate and save the Acceptance Criteria draft to .tmp/ac-draft-YYYYMMDD-1.md. The agent should allow iterative refinement by re-asking clarifying questions and regenerating the draft until approval.

Frequently Asked Questions about acceptance-criteria-drafter

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I draft acceptance criteria for a new feature requirement?▼

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.

What is the best way to generate testable requirements for GitHub Issues?▼

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.

Can I use an interview process to capture edge cases and non-functional requirements?▼

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.

How do I save acceptance criteria drafts as Markdown files for iterative refinement?▼

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.

Does the acceptance criteria drafting process support 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.

What format do I need for acceptance criteria to ensure verifiability?▼

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.