acceptance-test-writer

Generate YAML acceptance tests and a manifest from PRD documents.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/bjornslib/cobuilder-harness --skill acceptance-test-writer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: acceptance-test-writer
Source: https://github.com/bjornslib/cobuilder-harness/tree/main/.claude/skills/acceptance-test-writer
Command: npx skills add https://github.com/bjornslib/cobuilder-harness --skill acceptance-test-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Writing comprehensive acceptance tests from PRDs is time-consuming and error-prone; this skill automates converting PRD documents into structured, executable test definitions.

Core Features & Use Cases

  • Generate YAML-based acceptance tests from PRD documents.
  • Produce a manifest and per-criterion test files with clear traceability to PRD sections.
  • Support Guardian and Journey modes for end-to-end and exploratory validation.

Quick Start

Provide a PRD markdown file to the skill and run it to generate a complete acceptance-test suite.

Frequently Asked Questions about acceptance-test-writer

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

FAQPage Schema
How do I generate automated acceptance tests from a PRD?

To generate automated acceptance tests from a PRD, provide the markdown PRD document to the skill and run it to translate requirements into structured YAML test scripts and a manifest.

What is the best way to codify acceptance criteria from PRDs for automated validation?

Codifying acceptance criteria from PRDs for automated validation is best handled by generating per-criterion YAML test files with clear traceability to PRD sections, supporting multi-epic organization.

Can I organize acceptance test generation by epic across multiple PRD documents?

Yes, acceptance test generation supports multi-epic organization across PRD documents, producing a manifest and per-criterion YAML test files structured for your automated validation needs.

Does this test generation approach support end-to-end and exploratory validation scenarios?

End-to-end and exploratory validation scenarios are supported through Guardian and Journey modes, applying to PRD-driven product work where automated acceptance testing must cover complex flows.

Do I need a specific test framework to execute the generated YAML acceptance tests?

Executing the generated YAML acceptance tests requires a runner compatible with YAML test scripts and manifests, as the skill focuses on translating PRD requirements into executable test definitions rather than providing the execution environment.