name	test-driven-development
description	Required TDD loop for tasks that need red, green, refactor, final-green, and test-quality evidence.
version	1.0.0
category	core
triggers	tdd, test-driven development, red green refactor
metadata	{"gobby":{"audience":"agent","depth":1}}

Test-Driven Development

Use this when a task requires TDD.

Required Loop

Write or update the smallest meaningful test before implementation.
Run the exact test command and verify the expected failure.
Implement the smallest change that makes the new failing test pass: the minimal green step.
Run the exact test command and verify green.
Refactor only after green, then rerun final green validation.

Completion Evidence

The task handoff must include:

Red evidence: exact command and failure output summary from before implementation.
Green evidence: exact command and pass output summary after minimal implementation.
Refactor/final-green evidence: exact final command and pass output summary.
Test-quality audit evidence for touched test paths, or a specific reason it was not applicable.

When tests were added or heavily edited, run:

uv run gobby test-quality audit <paths> --baseline .gobby/test-quality-baseline.json --fail-on-new --min-severity high

TDD is not satisfied by writing tests after implementation, by only running a broad suite, or by omitting the expected red failure.

Más de este repositorio

mismo repositorio

code-index

GobbyAI/gobby

Instructions for using gcode CLI for code search and retrieval. Loaded on demand when project has a code index.

2026-05-2519

task-transitions

GobbyAI/gobby

Pre-transition checklist for closing or reviewing tasks. Covers fresh verification evidence, commits, and memory gates.

2026-05-2519

coderabbit

GobbyAI/gobby

Use when processing CodeRabbit review comments, CodeRabbit CLI reports, or `$gobby coderabbit [findings]` requests.

2026-05-2519

writing-skills

GobbyAI/gobby

Use when creating, editing, or validating Gobby skills, especially when a skill must change agent behavior or become discoverable through gobby-skills.

2026-05-2519

build-coordinator

GobbyAI/gobby

Use when coordinating a full gobby build run for an epic or task, especially when the user assigns the current session as coordinator, asks for a coordination epic, wants build agents/worktrees monitored, or wants gobby build bugs fixed so future runs work unattended.

2026-05-2419

gobby

GobbyAI/gobby

Router contract for provider-aware Gobby help and installed skill dispatch.

2026-05-2419

name	test-driven-development
description	Required TDD loop for tasks that need red, green, refactor, final-green, and test-quality evidence.
version	1.0.0
category	core
triggers	tdd, test-driven development, red green refactor
metadata	{"gobby":{"audience":"agent","depth":1}}

Test-Driven Development

Use this when a task requires TDD.

Required Loop

Write or update the smallest meaningful test before implementation.
Run the exact test command and verify the expected failure.
Implement the smallest change that makes the new failing test pass: the minimal green step.
Run the exact test command and verify green.
Refactor only after green, then rerun final green validation.

Completion Evidence

The task handoff must include:

Red evidence: exact command and failure output summary from before implementation.
Green evidence: exact command and pass output summary after minimal implementation.
Refactor/final-green evidence: exact final command and pass output summary.
Test-quality audit evidence for touched test paths, or a specific reason it was not applicable.

When tests were added or heavily edited, run:

uv run gobby test-quality audit <paths> --baseline .gobby/test-quality-baseline.json --fail-on-new --min-severity high

TDD is not satisfied by writing tests after implementation, by only running a broad suite, or by omitting the expected red failure.