write-tests

Generate failing test suites from acceptance criteria for TDD workflows.

Updated Jun 12, 2026

Search Tags:#automation #testing #tdd #quality assurance #software development #acceptance criteria

Ready to run

npx skills add https://github.com/ambrovia/agent-skills-pipeline --skill write-tests-ambrovia

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: write-tests
Source: https://github.com/ambrovia/agent-skills-pipeline/tree/main/skills/write-tests
Command: npx skills add https://github.com/ambrovia/agent-skills-pipeline --skill write-tests-ambrovia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents the common pitfall of writing implementation code before defining requirements, which often leads to code that confirms existing bugs rather than proving intended behavior.

Core Features & Use Cases

TDD Red Phase Enforcement: Ensures tests are written before any implementation code, creating a clear red-phase baseline.
Acceptance Criterion Mapping: Directly links every test to a specific work package acceptance criterion to prevent scope creep.
Combined Seam Validation: Mandates integration-level tests to ensure that individual components function correctly within the larger system flow.

Quick Start

Invoke the write-tests skill when you are ready to begin the build phase for a planned work package to generate the necessary failing test suite.

Frequently Asked Questions about write-tests

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

FAQPage Schema

How do I enforce failing tests before writing implementation code in a TDD workflow?▼

To enforce failing tests first in a TDD workflow, you generate test suites based on acceptance criteria before implementation begins. This creates a red-phase baseline that prevents code from confirming existing bugs rather than proving intended behavior.

How do I map acceptance criteria to software tests to prevent scope creep?▼

Mapping acceptance criteria to software tests involves directly linking every generated test to a specific work package requirement. This ensures strict requirement-first coding by verifying that each test structurally validates an intended behavior defined in the planned work package.

When do I need to generate failing test suites for test-driven development?▼

You need to generate failing test suites for test-driven development when you are ready to begin the build phase for a planned work package. This requirement-first process ensures structural verification and compile-time compliance before any implementation code is written.

Does TDD test generation support integration-level seam validation for component flows?▼

TDD test generation supports integration-level seam validation by mandating tests that ensure individual components function correctly within the larger system flow. This combined seam verification guarantees runtime compliance alongside compile-time checks.

What is the best way to automate quality assurance tests from acceptance criteria?▼

The best way to automate quality assurance tests from acceptance criteria is to generate failing test suites that enforce structural verification. This approach applies strict TDD workflows to software development tasks, ensuring code adheres to defined requirements.

Do I need project-specific testing rules to generate failing tests for TDD?▼

Yes, you need project-specific testing rules and verification commands to generate failing tests for TDD. Integration with these rules ensures that the generated test suites enforce both compile-time and runtime compliance within your software engineering environment.