aoa-tdd-slice

Implement a bounded feature slice using test-first discipline and verification.

4|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/8Dionysus/aoa-skills --skill aoa-tdd-slice
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aoa-tdd-slice
Source: https://github.com/8Dionysus/aoa-skills/tree/main/.agents/skills/aoa-tdd-slice
Command: npx skills add https://github.com/8Dionysus/aoa-skills --skill aoa-tdd-slice

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It enables developers to implement a small, bounded feature slice with confidence by defining behavior through tests before writing code, reducing regression risk and unnecessary refactoring.

Core Features & Use Cases

  • Test‑first workflow: Write or update tests that capture the desired behavior prior to implementation.
  • Minimal implementation: Make the smallest code change that satisfies the tests.
  • Explicit refactor boundaries: Keep refactoring confined to the defined slice.
  • Verification summary: Produce a concise report of added tests, code changes, and remaining out‑of‑scope behavior.
  • Use case: When adding a new API endpoint or fixing a specific bug, use this skill to ensure the change is well‑tested and isolated.

Quick Start

Ask the agent to run aoa-tdd-slice on the target module, describing the desired behavior and any constraints.

Frequently Asked Questions about aoa-tdd-slice

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

FAQPage Schema
How do I implement a small feature slice using test-first discipline?

To implement a feature slice using test-first discipline, you define the desired behavior by writing or updating tests before writing code, then make minimal code changes until the test suite passes.

When should I use a test-first approach for code refactoring?

Use a test-first approach for code refactoring when a specific behavior change is bounded and can be captured in tests, rather than during a broad rewrite or exploratory task.

What is the best way to add a new API endpoint without causing regressions?

The best way to add a new API endpoint without causing regressions is to capture the desired behavior in tests first, make minimal code changes to satisfy them, and keep refactoring confined to that slice.

How do I verify that my minimal code changes satisfy the new behavior tests?

You verify minimal code changes by running the test suite to confirm compliance, then review a verification summary detailing added tests, code changes, and remaining out-of-scope behavior.

Can I use this test-first workflow for a broad system rewrite?

No, this test-first workflow is designed for bounded feature slices and specific bug fixes, not for broad rewrites or exploratory tasks where behavior is not yet clearly defined.

What do I need to run a test-first feature slice implementation?

You need the ability to add or modify tests within your target module, make code changes, and run the existing test suite to verify that the new behavior is met.