skills.rest
hmcts
hmctsOFFICIAL
Explore all skills by this author →
Website𝕏@HMCTSgovukGitHub

write-acceptance-criteria

Generates Turn-by-turn acceptance criteria in GWT format for given stories.

3|4|Updated Apr 4, 2026
Search Tags:#acceptance criteria#software testing#requirements engineering#developer tool#GWT format
One-click install
npx skills add https://github.com/hmcts/agentic-plugins-marketplace --skill write-acceptance-criteria-hmcts
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-acceptance-criteria
Source: https://github.com/hmcts/agentic-plugins-marketplace/tree/main/plugins/skills/bdd-workflow/skills/write-acceptance-criteria
Command: npx skills add https://github.com/hmcts/agentic-plugins-marketplace --skill write-acceptance-criteria-hmcts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill aids in crafting clear, testable acceptance criteria for requirements or user stories, eliminating ambiguity and ensuring comprehensive coverage.

Core Features & Use Cases

  • AC Creation: Facilitates the writing of Given/When/Then (GWT) formatted acceptance criteria.
  • Guidance: Provides templates and rules for constructing effective ACs.
  • Use Case: Ideal for teams working on software development, where clear acceptance criteria are crucial for successful project delivery.

Quick Start

Use the 'write-acceptance-criteria' skill to generate acceptance criteria for a user story.

Frequently Asked Questions about write-acceptance-criteria

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

FAQPage Schema
How do I write acceptance criteria in Given/When/Then format?▼

This Skill generates acceptance criteria using the Given/When/Then format, ensuring testability and clarity in requirements documentation. It eliminates ambiguity by providing templates and rules for constructing effective acceptance criteria for user stories.

What is the Given/When/Then format for user stories?▼

The Given/When/Then format structures acceptance criteria by defining prerequisites, actions, and expected outcomes. It provides templates and rules to eliminate ambiguity and ensure comprehensive coverage in requirements documentation.

Can I generate testable acceptance criteria for software development requirements?▼

Yes, you can generate testable acceptance criteria for software development requirements. The Skill crafts clear criteria using the Given/When/Then format, ensuring comprehensive coverage and successful project delivery for application development teams.

What's the best way to structure acceptance criteria for application development?▼

The best way to structure acceptance criteria for application development is using the Given/When/Then format. This approach ensures testability and clarity, eliminating ambiguity in requirements documentation by providing templates for effective criteria construction.

Why does my acceptance criteria lack testability and clarity?▼

Your acceptance criteria may lack testability and clarity due to missing structured formatting. Applying the Given/When/Then format eliminates ambiguity by providing templates and rules that ensure comprehensive coverage and direct testability in requirements documentation.

Related Skills

Explore More Software Engineering Skills→
yknothingyknothing
1

acceptance-criteria

Define testable acceptance criteria for requirements using Given-When-Then or checklist formats.

Community
Intermediate
AnastasiyaWAnastasiyaW
140

plan-to-tickets

Decompose project plans into Markdown tickets with acceptance criteria.

Community
Intermediate
whimzyLivewhimzyLive
3

user-story

Generate user stories with structured Gherkin acceptance criteria.

Community
Intermediate
thesaifalitaithesaifalitai
8

feature-forge

Define feature specifications with EARS-format requirements and Given/When/Then acceptance criteria.

Community
Advanced