Skip to content
tdd · octo · Flowy
Test-driven development with red-green-refactor discipline
One command from octo .
$ npx -y skills add nyldn/claude-octopus --agent claude-codeShips with octo. Installing the plugin gets this command.
⚡ How it fires
How this command gets triggered: by you, by Claude, or both.
Fires itself Claude auto-loads it when your prompt matches the work. You can call it Invoke it directly when you want it. Slash command /tdd👁️ Context preview
What this command does when you run it.
Test-driven development with red-green-refactor discipline </> Command definition
tdd.md
---
command : tdd
description : Test-driven development with red-green-refactor discipline
---
# TDD - Test-Driven Development Skill
**Your first output line MUST be:** `🐙 Octopus TDD Mode`
## 🤖 INSTRUCTIONS FOR CLAUDE
When the user invokes this command (e.g., `/octo:tdd <arguments>`):
### Step 1: Ask Clarifying Questions
**CRITICAL: Before starting TDD, use the AskUserQuestion tool to gather context:**
Ask 3 clarifying questions to ensure appropriate test strategy:
```javascript
AskUserQuestion({
questions: [
{
question: "What's your test coverage goal?",
header: "Coverage",
multiSelect: false,
options: [
{label: "Critical paths only", description: "Focus on business-critical flows"},
{label: "Standard coverage ~80%", description: "Industry-standard coverage target"},
{label: "Comprehensive >90%", description: "High coverage for safety-critical code"},
{label: "Full mutation testing", description: "Maximum rigor with mutation tests"}
]
},
{
question: "What test style fits this feature?",
Flowy AI Flows that just work. Hand-picked Claude Code plugins that fire the right skill as you prompt.
header: "Test Style",
multiSelect: false,
options: [
{label: "Unit tests focus", description: "Isolated component testing"},
{label: "Integration tests", description: "Module interaction testing"},
{label: "E2E tests", description: "Full user flow testing"},
{label: "Mix of all", description: "Test pyramid approach"}
]
},
{
question: "What's the complexity level of this feature?",
header: "Complexity",
multiSelect: false,
options: [
{label: "Simple CRUD", description: "Basic create/read/update/delete"},
{label: "Moderate business logic", description: "Some conditional logic and validation"},
{label: "Complex algorithms", description: "Significant computation or logic"},
{label: "Distributed systems", description: "Multiple services, async, eventual consistency"}
]
}
]
})
```
**WAIT for the user's answers before proceeding.**
**After receiving answers, incorporate them into the TDD approach and test depth.**
### Step 2: Execute TDD
Read and follow the full skill instructions from:
`${HOME}/.claude-octopus/plugin/.claude/skills/skill-tdd/SKILL.md`
Apply the user's answers from Step 1 as the TDD scope and test depth.
---
**Auto-loads the `skill-tdd` skill for test-first development.**
## Quick Usage
Just use natural language:
```
"Use TDD to implement the authentication feature"
"Write tests first for the payment processing"
"TDD approach for the new API endpoint"
```
## TDD Workflow
1. **Red**: Write a failing test
2. **Adversarial Review**: Challenge test design with a second provider — surfaces missing scenarios, boundary conditions, and tests that could pass with a stub (skip with `--fast`)
3. **Green**: Write minimal code to pass
4. **Refactor**: Improve code quality
5. **Repeat**: Continue cycle
## What You Get
- Test-first approach enforcement
- Red-green-refactor discipline
- Comprehensive test coverage
- Clean, testable code
- Regression prevention
## Natural Language Examples
```
"Use TDD to build a user registration feature"
"Test-driven development for the shopping cart"
"Write tests first for the authentication system"
```
© 2026 Flowy · Free and open source
Built for Claude Code · Not affiliated with Anthropic
