Help us improve
Share bugs, ideas, or general feedback.
From tech-lead
This skill orchestrates full-cycle TDD development by integrating multiple specialized plugins into a cohesive workflow.
npx claudepluginhub ruslan-korneev/claude-plugins --plugin tech-leadHow this skill is triggered — by the user, by Claude, or both
Slash command
/tech-lead:tdd-workflowThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill orchestrates full-cycle TDD development by integrating multiple specialized plugins into a cohesive workflow.
Creates TDD implementation plans enforcing strict Red-Green-Commit/Rollback cycles per step. Auto-activates for TDD commands, references, or test-critical features.
Orchestrates RED/GREEN/REFACTOR TDD cycles using context-isolated Task sub-agents. Use for test-first feature implementation with structured BDD outer loop support.
Share bugs, ideas, or general feedback.
This skill orchestrates full-cycle TDD development by integrating multiple specialized plugins into a cohesive workflow.
Use this skill when the user wants to:
Trigger phrases:
┌─────────────────────────────────────────────────────────┐
│ TDD CYCLE │
│ │
│ ┌─────────┐ ┌─────────┐ ┌───────────┐ │
│ │ RED │───▶│ GREEN │───▶│ REFACTOR │──┐ │
│ │ Write │ │ Make │ │ Improve │ │ │
│ │ Failing│ │ Test │ │ Code │ │ │
│ │ Test │ │ Pass │ │ Quality │ │ │
│ └─────────┘ └─────────┘ └───────────┘ │ │
│ ▲ │ │
│ └────────────────────────────────────────┘ │
│ │
└─────────────────────────────────────────────────────────┘
| Phase | Agent | Model | Purpose |
|---|---|---|---|
| Explore | codebase-explorer | sonnet | Fast module discovery |
| Plan | planning-agent | opus | Deep analysis, user questions |
| Execute | execution-agent | opus | TDD implementation |
This workflow integrates with existing plugins:
User Prompt
│
▼
┌─────────────────┐
│ Codebase │ Find relevant modules
│ Explorer │ Understand project structure
└────────┬────────┘
│
▼
┌─────────────────┐
│ Planning │ Ask clarifying questions
│ Agent │ Create development plan
└────────┬────────┘ Define test cases
│
▼
┌─────────────────┐
│ EnterPlanMode │ User reviews and approves
│ (Claude Code) │ the development plan
└────────┬────────┘
│
▼
┌─────────────────┐
│ Execution │ TDD cycle for each test
│ Agent │ Quality gates
└────────┬────────┘ Documentation
│
▼
Completed Feature
Plans include Memory Anchors — structured context that persists across sessions:
---
id: dev-{uuid}
feature: {name}
status: draft | approved | in_progress | completed
---
Anchors capture:
Each TDD phase should be tracked explicitly. Use TaskCreate to make phase transitions visible:
TaskCreate: "RED — Write failing test for <feature>"
→ Write test, verify it fails
→ TaskUpdate: completed
TaskCreate: "GREEN — Minimal implementation for <feature>"
→ Write just enough code to pass
→ TaskUpdate: completed
TaskCreate: "REFACTOR — Clean up <feature> implementation"
→ Improve code quality, tests stay green
→ TaskUpdate: completed
Why: Without explicit separation, phases blur together. Developers skip Red (writing tests after code) or skip Refactor (moving on too quickly). Tracking forces discipline.