Menu

Individual skill

tdd

Test-first cycle and red-step evidence rule for skills that implement behavior a test can assert. Binds when the verification skill resolves a test command; defines what the red run must quote and when the cycle is skipped with a reason.

plugins/yagizdo/quiver/skills/tdd/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,537
Repository last updated
Nov 7, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# TDD

Reference skill read by `/plan` Step 5, `/work` Phase 3 and `skills/work/orchestrator.md`, and `/hypothesis-debugging` Step 7; `/ship` names it where it hands the build to `/work`. It is never invoked and runs nothing itself: the consumer resolves the test command per `skills/verification/SKILL.md`, follows the cycle here, and quotes the evidence.

## Applicability

The cycle binds to a change when both hold:

- The consumer resolved the test command per `skills/verification/SKILL.md` and the value is not `none`.
- The change produces behavior a test can assert. Documentation, a config value, a rename with no behavior change, and a migration with no code path do not.

When either fails, the outcome is `skipped: <reason>`, and the reason names which one: `test command none (<verification's reason>)` or `no testable behavior (<what the change is>)`. A skipped cycle is a recorded fact, not an error, and it never blocks the consumer.

The user's own project instructions win. A project whose `CLAUDE.md` says not to use TDD settles it.