comprehensive-tdd-planning

name	comprehensive-tdd-planning
version	2.0.0
description	TDD planning with agent-per-file execution. Planning is verbose. Agent files are minimal execution context.

Comprehensive TDD Planning v2.0.0

Architecture

Phase	Verbosity	Purpose
Planning (plan.md)	Verbose	Figure things out, iterate, full specs
Execution (*.agent.md)	Minimal	Distilled context for agent, ~200-400 lines

Directory Structure

NNNN-descriptive-name/
├── README.md           # Index, dependency graph, status matrix
├── plan.md             # Full verbose feature specs (planning reference)
├── interfaces.md       # Contract source of truth
├── gotchas.md          # Discovered issues (append-only)
└── agents/
    └── NNN_agent_[name].agent.md # Minimal execution context per agent (zero-padded)

Agent Files: Design Principles

Agent files are distilled execution context, not documentation.

IN Agent Files

• Feature IDs + one-line TL;DRs
• Interface contracts (your exports + what you receive)
• Files to create/modify
• Test IDs
• Concise TDD cycles (one line per cycle)
• Relevant gotchas (brief)
• Done checklist

OUT of Agent Files

• Verbose Gherkin (TL;DR sufficient)
• Methodology explanations (agent knows TDD)