tdd-feature-agent

Identify pending features from features.json and delegate implementation to the coder agent.

Updated Jan 17, 2026
One-click install
npx skills add https://github.com/chijunzheng/ShowMe --skill tdd-feature-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-feature-agent
Source: https://github.com/chijunzheng/ShowMe/tree/main/.claude/skills/tdd-feature-agent
Command: npx skills add https://github.com/chijunzheng/ShowMe --skill tdd-feature-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates feature development by delegating work to specialized sub-agents to ensure focused execution, clean handoffs, and faster delivery.

Core Features & Use Cases

  • Central coordination: reads progress/context and delegates tasks to the coder, code-review, tdd-debugger, and deep-dive agents.
  • Safe handoffs: spins up fresh context windows for each sub-agent to maintain task isolation.
  • Failure recovery: routes failures to tdd-debugger or deep-dive for root-cause analysis and remediation.

Quick Start

Initiate the orchestration by selecting the next feature from features.json and spawning a coder agent to implement it.

Frequently Asked Questions about tdd-feature-agent

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

FAQPage Schema
How do I orchestrate feature development across multiple agents?

Orchestrating feature development across multiple agents requires central coordination to read progress, delegate tasks to a coder, and manage handoffs. This ensures focused execution and clean context isolation for each sub-agent.

What's the best way to automate code review after a feature is implemented?

Automating code review after implementation involves delegating the completed feature to a code-review agent. The orchestrator initiates this review immediately after the coder agent finishes the assigned feature work.

How do you handle test failures during automated agent workflows?

Handling test failures in automated workflows requires routing the failed execution to a debugger or deep-dive agent. These specialized agents perform root-cause analysis and remediation to resolve the underlying issues.

Why use isolated context windows when delegating coding tasks to agents?

Isolated context windows are used when delegating coding tasks to maintain safe handoffs and task isolation. Spinning up fresh contexts prevents cross-contamination of instructions and ensures each agent focuses strictly on its specific objective.

Can I track pending feature dependencies using a JSON file for agent orchestration?

Tracking pending feature dependencies using a JSON file provides the central context needed for agent orchestration. The coordinator identifies the next pending feature and its dependencies directly from this file to initiate implementation.

Does agent orchestration work for recovering from debugging failures in feature workflows?

Agent orchestration works for recovering from debugging failures by automatically engaging deep-dive agents. These agents analyze root causes of failed tests and update progress tracking accordingly to resume the workflow.