tdd

Turn approved specs into scenario recipes, implementation contracts, and worker-task handoffs.

5|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/friedbotstudio/baseline --skill tdd-friedbotstudio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/friedbotstudio/baseline/tree/main/.claude/skills/tdd
Command: npx skills add https://github.com/friedbotstudio/baseline --skill tdd-friedbotstudio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The TDD skill coordinates the planning phase that turns an approved spec or quickfix request into a concrete, test-first execution plan, so the harness can move from intake to implementation without losing scope or order.

Core Features & Use Cases

  • Decides the scenario recipe for each acceptance criterion and clearly names out-of-scope cases.
  • Builds the implementation contract, including failing test paths, write set, behavior excerpts, and project conventions.
  • Writes the coordinator state file, seeds sequential worker tasks, and prepares inlined verification and drift analysis for a disciplined handoff.
  • Use it when a workflow is ready to move from approved spec into scenario design, implementation, verification, and drift checking.

Quick Start

Ask the tdd skill to read the approved spec or quickfix brief and produce the scenario recipe, implementation contract, task seed, and harness continuation state for the next phase.

Frequently Asked Questions about tdd

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

FAQPage Schema
How do I turn an approved spec into a test-first execution plan?

Turn an approved spec into a test-first execution plan by generating a scenario recipe, implementation contract, and sequential worker task seeds. This coordinates the transition from intake to implementation without losing scope.

What is the best way to orchestrate sequential worker execution for TDD workflows?

Orchestrate sequential worker execution for TDD workflows by using a harness that seeds tasks, writes a coordinator state file, and prepares inlined verification to maintain strict test-first implementation order.

How do I generate an implementation contract with failing test paths and behavior excerpts?

Generate an implementation contract by defining failing test paths, write sets, behavior excerpts, and project conventions from an approved spec. This establishes clear boundaries for scenario design and subsequent verification.

Does test-driven development workflow orchestration support quickfix development flows?

Test-driven development workflow orchestration supports both spec-backed and quickfix development flows, producing the state file, TaskList seed, and drift-check handoff required for structured implementation.

How do I perform a drift check after scenario design and implementation?

Perform a drift check after scenario design by preparing inlined verification and drift analysis during the handoff phase, ensuring the implementation matches the approved spec without unmanaged deviations.

Why do I need a harness continuation marker for spec to implementation tasks?

A harness continuation marker is needed for spec to implementation tasks to maintain workflow orchestration state, allowing the system to resume phase-6 execution and sequential worker tasks without losing progress.