tdd

Plan and execute tracer-bullet test cycles for Brain OS skills.

16|9|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/sonthanh/brain-os-plugin --skill tdd-sonthanh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/sonthanh/brain-os-plugin/tree/main/skills/tdd
Command: npx skills add https://github.com/sonthanh/brain-os-plugin --skill tdd-sonthanh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Test-driven development discipline for brain-os artifacts ensures reliable behavior by validating changes through public interfaces rather than internal details.

Core Features & Use Cases

  • Tracer-bullet workflow: one test, one implementation, one refactor cycle to validate real-world skill behavior.
  • Public-interface focus: tests validate observable behavior from the outside, not internal implementation.
  • Usage scenarios: building or fixing skills, scripts, hooks, plists, or vault tooling.

Quick Start

Invoke /tdd to start a tracer bullet cycle by writing one end-to-end test for the target behavior and then implementing the minimal code to pass.

Frequently Asked Questions about tdd

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

FAQPage Schema
What is a tracer-bullet workflow in test-driven development?

A tracer-bullet workflow in test-driven development validates real-world behavior by running end-to-end cycles where you write one failing test, implement minimal code to pass, then refactor only after green.

How do I start a TDD cycle for validating skill behavior?

Start a TDD cycle by writing one end-to-end test for the target observable behavior, then implement the minimal code required to pass that test before refactoring.

Does test-driven development focus on internal implementation or public interfaces?

Test-driven development for brain-os artifacts focuses on public interfaces, validating observable behavior from the outside rather than testing internal implementation details.

When should I use TDD for building or fixing scripts and vault tooling?

Use TDD when building or fixing skills, scripts, hooks, plists, or vault tooling to ensure reliable behavior through disciplined test cycles before implementation.

How are TDD cycle results recorded in the vault?

All TDD cycle results are recorded in the vault under daily/skill-outcomes/tdd.log according to established skill-spec conventions.