TDD

Use this skill as a single-user workflow. Do not introduce worker, task assignment, or team coordination concepts.

Core Rules

• Read the request, relevant code, and constraints before implementing.
• Define what counts as done before writing production code.
• Prefer a red phase when the task supports automated tests.
• Do not default to E2E. Use E2E only when explicitly requested, already required by the task contract, or when lower-cost verification cannot cover the acceptance risk.
• If the task needs test-case design, regression planning, acceptance coverage, or broader QA execution, invoke qa-expert instead of expanding this skill into a full QA workflow.
• If automated tests are not appropriate, define manual verification before implementing.
• Do not treat the work as complete until verification finishes.
• If verification is skipped, state the reason and residual risk explicitly.

Workflow

Follow this sequence: