acp-test-first

Write a failing test before implementing code changes.

29|12|Updated May 4, 2026
One-click install
npx skills add https://github.com/bravekingzhang/agent-coding-playbook --skill acp-test-first
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: acp-test-first
Source: https://github.com/bravekingzhang/agent-coding-playbook/tree/main/skills/acp-test-first
Command: npx skills add https://github.com/bravekingzhang/agent-coding-playbook --skill acp-test-first

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps in implementing code changes in a structured, test-driven manner, ensuring that changes adhere to expected behavior before they are made to the codebase.

Core Features & Use Cases

  • Test-Driven Development: Ensures that code changes are validated by tests before implementation.
  • Bug Fixes: Assists in writing failing tests for bugs before writing the code to fix them.
  • Behavior Changes: Guides the process for adding new features while maintaining existing functionality.
  • Refactoring: Ensures refactoring does not break existing functionality.

Quick Start

Use this skill to create a failing test for a new feature before writing the code for the feature.

Frequently Asked Questions about acp-test-first

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

FAQPage Schema
How do I implement test-driven development for bug fixes and new features?

Test-driven development for bug fixes and features is implemented by first writing a failing test for the desired behavior, then writing the minimum code required to pass that test.

Do I need an existing test framework to use test-driven development for code changes?

Yes, an existing test framework is required. This approach applies to projects with a test framework to validate behavior changes and ensure code correctness before implementation.

What is the best way to ensure refactoring does not break existing functionality?

To ensure refactoring does not break existing functionality, implement changes in a test-driven way by validating code changes against expected behavior before applying them to the codebase.

How does writing a failing test before coding improve code quality?

Writing a failing test before coding improves code quality by structuring development to ensure changes adhere to expected behavior, validating correctness before modifying the codebase.

Can I use this test-driven approach for behavior changes in existing projects?

Yes, you can use this test-driven approach for behavior changes in existing projects. It guides adding new features or fixing bugs while maintaining existing functionality through structured validation.