Library use: Apply the compatibility and execution contract. Source roles, memory claims, command names, hooks, and integrations are instructions or prerequisites—not installed capabilities.

Tdd

When to use

Use tests to define behavior, implement minimally, then verify the resulting change.

Inputs

User objective, project constraints, relevant source or evidence, and explicit success criteria.

Procedure and handoffs

1. Load the tdd-guide procedure. Define behavior and failure cases; choose language-specific testing skills.
2. Load the tdd-workflow procedure. Capture RED evidence, implement GREEN, and refactor with tests remaining green.
3. Load the verification-loop procedure. Verify broader project checks; report the selected coverage target and actual result.

Verification and output

Produce the artifacts required by the selected procedures and an evidence-backed status: completed, failed, skipped with reason, or blocked on a named prerequisite. Carry unresolved findings forward. Do not treat an unavailable tool, an unrun check, or a reviewer failure as a pass.

Scope and compatibility

Select stages proportionate to the task. Preserve required gates of the chosen variant; record exceptions. Read the compatibility policy before combining conflicting variants. These instructions do not grant tool access or authorize publishing, commits, deployment, or communications.

Related skills and principles

• core/goal-driven-execution
• core/simplicity-first
• core/surgical-changes
• core/think-before-coding
• testing/tdd-guide
• testing/tdd-workflow
• verification/verification-loop

Source provenance

• ecc/agents/tdd-guide.md
• ecc/skills/tdd-workflow/SKILL.md
• ecc/skills/verification-loop/SKILL.md