start-tdd

Orchestrate TDD feature implementation with Task Master slices and parallel agent groups.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Samaara-Das/money-hungry-games --skill start-tdd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: start-tdd
Source: https://github.com/Samaara-Das/money-hungry-games/tree/main/.claude/skills/start-tdd
Command: npx skills add https://github.com/Samaara-Das/money-hungry-games --skill start-tdd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drive feature implementation in a controlled, test-first manner by orchestrating PRD parsing, slice creation, and cross-team coordination using Task Master CC tasks.

Core Features & Use Cases

  • Orchestrates PRD parsing into structured slices using Task Master, analyzes complexity, and expands tasks to a practical work breakdown.
  • Groups work into backend and frontend agents with coordinated CC tasks, enabling parallel progress on independent slices.
  • Enforces a RED-GREEN iterative loop with tdd-writer and implementer sub-agents, while logging progress and ensuring no step is skipped.

Quick Start

Initialize a TDD session by ensuring a PRD exists at .claude/prd-[feature-name].md and then invoke the start-tdd skill.

Frequently Asked Questions about start-tdd

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

FAQPage Schema
How do I automate test-driven development for backend and frontend feature slices?

Automating test-driven development for backend and frontend slices requires orchestrating parallel agent groups with coordinated CC tasks. This Skill parses your PRD into structured slices, groups work by team, and enforces strict RED-GREEN iterative loops to ensure no step is skipped.

What is the best way to orchestrate TDD cycles using a PRD?

The best way to orchestrate TDD cycles from a PRD is to automate complexity analysis and task expansion into practical work breakdowns. By generating Task Master slices and applying strict RED-first testing loops, teams achieve controlled, cross-team feature implementation.

How does TDD orchestration handle parallel work across independent feature slices?

TDD orchestration handles parallel work by grouping slices into backend and frontend agents with coordinated CC tasks. This structure enables parallel progress on independent slices while maintaining strict RED-GREEN iterative loops through tdd-writer and implementer sub-agents.

Do I need a PRD before starting a TDD-driven feature implementation session?

Yes, you need a PRD located at .claude/prd-[feature-name].md before starting a TDD-driven feature implementation session. The Skill parses this document to analyze complexity, expand tasks into slices, and generate the coordinated backend and frontend CC tasks.

Can I use this TDD orchestration approach for projects without existing Task Master tasks?

Yes, this approach applies to feature development projects where PRDs exist but Task Master tasks are not yet generated. The Skill automates PRD parsing, creates structured slices, and generates the CC tasks needed to drive the RED-GREEN test loops.

When should I not use automated TDD orchestration for feature development?

You should not use automated TDD orchestration when a PRD does not exist or when the feature lacks distinct backend and frontend components. The orchestration relies on parsing a PRD into structured slices and coordinating parallel agent groups for cross-team work.