test-driven-development

Installation
SKILL.md

Test-Driven Development

Purpose

Prove every behavior change with a test that was watched failing and then passing. A test never seen failing may test nothing; implementation written before its test has no executable specification.

Workflow

  1. Use the existing observable/public boundary by default: tests live where behavior can be observed without reaching inside. Name the seam and its rationale before writing the test. Ask the user only when seam placement is genuinely uncertain, because unnecessary confirmation delays a testable behavior slice.
  2. Restate the required behavior as a testable assertion and pick the smallest next behavior slice.
  3. RED: write the test first. Before running it, verify explicit authorization for test execution exists in the current request; test permission does not authorize implicit restore or build.
  4. GREEN: write the minimal implementation that passes. Before running it, independently verify explicit authorization for test execution and any restore/build required by the command. If restore or build is not authorized, use existing prerequisites or record the exact gap.
  5. REFACTOR: only cleanup that keeps the suite green, rerunning after each step when each required operation is explicitly authorized. Without authorization, record refactoring as unverified rather than claiming the suite is green.
  6. Keep the test with the change. Repeat the cycle per behavior slice until the request is covered.

Output Contract

Installs
4
First Seen
Oct 13, 2026