Acceptance Criteria

Scaffolds an acceptance criteria framework using Given/When/Then BDD structure. Includes a reusable template for writing criteria, example Gherkin feature files, and an optional definition of done checklist. Provides a consistent format for capturing expected behavior across features and user stories.

Name	acceptance-criteria
Version	0.1.0
Category	qa
License	Apache-2.0
Persona	qa
Tags	testing, qa, bdd, gherkin, acceptance-criteria
Source	templates/acceptance-criteria

Render it

Three front doors, one catalog. Pick whichever suits the caller.

# CLI
npx @nanohype/sdk render acceptance-criteria --out ./my-app

# SDK
import { LocalSource, renderTemplate } from "@nanohype/sdk";
const result = await renderTemplate(source, "acceptance-criteria", variables);

# MCP — from an agent
get_template({ name: "acceptance-criteria" })

Variables

Required

ProjectName string

Kebab-case project name, used in document titles and directory Must be lowercase kebab-case starting with a letter.

Optional

Format string — defaults to gherkin

Criteria format style (e.g., gherkin, tabular, narrative)

IncludeDoD bool — defaults to true

Include a definition of done checklist document

What it produces

4 files. Placeholder names such as __APP_NAME__ are what the renderer substitutes into.

criteria/definition-of-done.md
criteria/examples/checkout.feature
criteria/examples/login.feature
criteria/template.md

Composes with

• Pairs with test-plan
• Pairs with test-automation
• Pairs with prd-template
• Nests inside monorepo

Composites that use it

• Product Launch — Full product launch kit spanning engineering, design, QA, product, marketing, and operations.