spec-to-tests

Convert Build Brief acceptance criteria into failing tests and reproducers.

2|1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/bigeasyfreeman/adlc --skill spec-to-tests-bigeasyfreeman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-to-tests
Source: https://github.com/bigeasyfreeman/adlc/tree/main/skills/spec-to-tests
Command: npx skills add https://github.com/bigeasyfreeman/adlc --skill spec-to-tests-bigeasyfreeman

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the issue of creating tests and reproducers directly from Build Brief acceptance criteria, ensuring that coding begins only after verification has failed.

Core Features & Use Cases

  • Acceptance Criteria Conversion: Converts acceptance criteria into failing tests and reproducers.
  • Context Assembly: Integrates Build Brief context to define tests and reproducers.
  • Verifier Artifacts: Produces failing verifier artifacts that guide the coding process.
  • Task Class Handling: Supports different task types like feature, bugfix, and build validation.
  • Quality Gates: Enforces a set of quality gates before finalizing tests.

Quick Start

Use the spec-to-tests skill to create failing tests from the given Build Brief context and acceptance criteria.

Frequently Asked Questions about spec-to-tests

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

FAQPage Schema
How do I generate failing tests from acceptance criteria before starting development?

Generate failing tests from acceptance criteria by converting Build Brief context into verifier artifacts and reproducers, ensuring coding begins only after verification has failed. This approach enforces test-first development within an AI-assisted engineering lifecycle.

Can I create reproducers for bugfix tasks using Build Brief context?

Yes, you can create reproducers for bugfix tasks by assembling Build Brief context and converting the acceptance criteria into failing tests. The process handles different task classes including feature, bugfix, and build validation.

What is the process for converting Build Brief acceptance criteria into test cases?

Converting Build Brief acceptance criteria into test cases involves parsing the input, assembling the context, and generating failing verifier artifacts. Quality gates are enforced before finalizing the tests to guide the subsequent coding process.

Do I need Python libraries to validate input and execute tests generated from acceptance criteria?

Yes, you need Python libraries to validate input, parse data, and execute tests generated from acceptance criteria. These libraries are required to support the parsing and execution phases of the test generation process.

What distinguishes generating tests from Build Brief acceptance criteria versus writing tests manually?

Generating tests from Build Brief acceptance criteria produces failing verifier artifacts directly from defined context, strictly enforcing a test-first workflow. Manual test writing lacks this automated context assembly and built-in quality gate enforcement.