mh-cto-sdlc-acceptance-criteria

Generate acceptance criteria from story specifications and domain model invariants.

2|Updated Apr 5, 2026

Search Tags:#TDD #acceptance criteria #software testing #acceptance testing #story specification

Ready to run

npx skills add https://github.com/Imad-Oute/MicroHard --skill mh-cto-sdlc-acceptance-criteria

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mh-cto-sdlc-acceptance-criteria
Source: https://github.com/Imad-Oute/MicroHard/tree/main/src/departments/cto/sdlc/phase-2-product-definition/mh-cto-sdlc-acceptance-criteria
Command: npx skills add https://github.com/Imad-Oute/MicroHard --skill mh-cto-sdlc-acceptance-criteria

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the generation of acceptance criteria for software development, streamlining the process and ensuring comprehensive test coverage.

Core Features & Use Cases

Automated AC Generation: Derives testable acceptance criteria directly from story specifications.
Synthesize-First Mode: Focuses on synthesizing ACs from story behaviors and domain model invariants.
Use Case: Ideal for product managers and QA teams to create a clear and actionable set of acceptance criteria for each story in an epic.

Quick Start

Run the skill with the command: /mh-cto-sdlc-acceptance-criteria

Frequently Asked Questions about mh-cto-sdlc-acceptance-criteria

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

FAQPage Schema

How do I automate acceptance criteria generation for software development stories?▼

You can automate acceptance criteria generation by using a Skill that extracts and synthesizes testable criteria directly from story specifications and domain model invariants. This streamlines the process and ensures comprehensive test coverage for your development cycle.

What is the best way to derive acceptance criteria from story specifications and domain invariants?▼

Deriving acceptance criteria from story specifications requires a synthesize-first approach that focuses on story behaviors and domain invariants. This method ensures that the generated criteria are directly tied to core software requirements and structural rules.

How does TDD discipline impact acceptance testing and story specification?▼

TDD discipline impacts acceptance testing by requiring knowledge of story anatomy and domain invariants to generate meaningful criteria. This ensures that story specifications translate directly into testable behaviors, maintaining alignment between development and testing.

Do I need knowledge of domain invariants to create testable acceptance criteria?▼

Yes, knowledge of domain invariants is required to create testable acceptance criteria. The Skill uses these invariants alongside story anatomy to accurately extract and synthesize the specific behaviors that the software testing process must validate.

Can I use this automated acceptance criteria tool for QA teams and product managers?▼

Yes, this automated acceptance criteria tool is ideal for both product managers and QA teams. It helps them create clear, actionable sets of acceptance criteria for each story within an epic, ensuring comprehensive test coverage and streamlined validation.

What are the limitations of synthesizing acceptance criteria from story behaviors?▼

The main limitation of synthesizing acceptance criteria from story behaviors is the strict prerequisite for well-defined story anatomy and explicit domain model invariants. Without precise input specifications and TDD discipline, the automated extraction may lack the accuracy needed for comprehensive testing.