user-story-ac-writer

Generate INVEST-compliant user stories with Gherkin acceptance criteria.

154|75|Updated May 9, 2026

Search Tags:#qa #agile #backlog #invest #gherkin #acceptance-criteria #user-story

Ready to run

npx skills add https://github.com/phucnt-bazone-vietnam/ba-zone-user-story-ac-writer --skill user-story-ac-writer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: user-story-ac-writer
Source: https://github.com/phucnt-bazone-vietnam/ba-zone-user-story-ac-writer/tree/main
Command: npx skills add https://github.com/phucnt-bazone-vietnam/ba-zone-user-story-ac-writer --skill user-story-ac-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps BA/PO produce high-quality User Stories and Acceptance Criteria that adhere to INVEST and Gherkin formats, reducing back-and-forth and misalignment.

Core Features & Use Cases

Enforce 6 INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable)
Generate Acceptance Criteria in Given-When-Then format with at least 3 scenarios (happy path, edge case, negative)
Support 3 modes: new US from feature description, refine existing US, and add AC for an existing US
Provide templates and references to guide quality checks, domain-specific customization, and a robust quality checklist

Quick Start

Provide a feature description or PRD to generate a complete US and AC.

Frequently Asked Questions about user-story-ac-writer

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

FAQPage Schema

How do I write user stories that follow the INVEST criteria for agile backlog refinement?▼

User stories following INVEST criteria must be Independent, Negotiable, Valuable, Estimable, Small, and Testable. This Skill enforces all six standards automatically, transforming raw feature descriptions into structured, INVEST-compliant backlog items ready for agile planning.

What is the best way to generate Gherkin acceptance criteria with Given-When-Then format?▼

Gherkin acceptance criteria use a Given-When-Then format to define test scenarios. This Skill generates them automatically, producing at least three scenarios per story covering happy paths, edge cases, and negative paths to ensure comprehensive QA validation.

Can I refine an existing user story and add missing acceptance criteria to my backlog?▼

Yes, you can refine existing user stories and augment missing acceptance criteria. The Skill supports refining current stories and adding Given-When-Then acceptance criteria, ensuring your existing backlog items meet INVEST compliance and QA validation requirements.

How do I structure acceptance criteria for edge cases and negative scenarios in agile development?▼

Acceptance criteria for edge cases require structured scenarios beyond the happy path. This Skill generates Gherkin-formatted criteria with at least three scenarios per user story, explicitly covering edge cases and negative paths alongside the standard happy path for robust QA.

Does this user story writer support feature descriptions from a PRD for sprint planning?▼

Yes, it processes feature descriptions or PRD inputs directly. The Skill converts these inputs into complete user stories with metadata and acceptance criteria, providing structured content that bridges product requirements and sprint planning for BA/PO workflows.

When should I use Gherkin format for user story acceptance criteria?▼

Gherkin format is needed when user stories require structured, testable acceptance criteria for QA validation. This Skill applies Given-When-Then formatting to define clear scenarios, reducing misalignment between development and testing teams during backlog refinement.