Combines Ralph Wiggum loops with structured feature plans for automated TDD-driven development. Creates phase-based plans with quality gates, then executes each phase using Ralph loops with Beads for persistent state tracking. Includes E2E testing with Playwright agents. Use for automated overnight development, complex feature implementation, or when you want AI to iterate until tests pass.
Executes automated TDD development with Ralph Wiggum loops, Beads persistence, and Playwright E2E testing.
/plugin marketplace add Henry229/alsso-plugin/plugin install henry229-auto-tdd-executor-auto-tdd-executor@Henry229/alsso-pluginThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Automated TDD development with Ralph Wiggum loops, Beads persistence, and Playwright E2E testing.
┌──────────────────────────────────────────────────────────────────────┐
│ Auto TDD Executor │
├──────────────────────────────────────────────────────────────────────┤
│ │
│ ┌─────────────┐ ┌─────────────┐ ┌─────────────────────────┐ │
│ │ Feature │───▶│ Ralph │───▶│ Beads │ │
│ │ Planner │ │ Wiggum │ │ (Persistence) │ │
│ └─────────────┘ └─────────────┘ └─────────────────────────┘ │
│ │ │ │ │
│ ▼ ▼ ▼ │
│ Phase-based TDD Loop Survives context │
│ Quality Gates Red-Green-Refactor compaction │
│ │
│ ┌────────────────────────────────────────────────────────────────┐ │
│ │ E2E Test Phase │ │
│ │ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ │ │
│ │ │ Playwright │ │ Playwright │ │ Playwright │ │ │
│ │ │ Planner │ │ Generator │ │ Healer │ │ │
│ │ └─────────────┘ └─────────────┘ └─────────────┘ │ │
│ └────────────────────────────────────────────────────────────────┘ │
│ │
└──────────────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────────────┐
│ Full Development Loop │
├─────────────────────────────────────────────────────────────────────┤
│ │
│ 1. PLAN │
│ └─▶ /auto-tdd-start │
│ └─▶ Create Beads issues from plan │
│ │
│ 2. IMPLEMENT (TDD) ┌───────────────┐ │
│ └─▶ /auto-tdd-run │ │ │
│ ├─▶ 🔴 RED: Write failing tests ────────┤ Ralph │ │
│ ├─▶ 🟢 GREEN: Implement minimal code ───┤ Wiggum │ │
│ ├─▶ 🔵 REFACTOR: Improve quality ───────┤ Loop │ │
│ └─▶ ✅ Unit Tests Pass ─────────────────┘ │ │
│ │ │
│ 3. E2E TEST ▼ │
│ └─▶ /auto-tdd-e2e ┌───────────────┐ │
│ ├─▶ playwright-test-planner ────────────┤ Parallel │ │
│ ├─▶ playwright-test-generator ──────────┤ Agents │ │
│ └─▶ If fail: playwright-test-healer ────┘ │ │
│ │ │
│ ├─── FAIL ──▶ Back to Step 2 (fix bugs) │
│ │ │
│ ▼ │
│ 4. QUALITY GATE │
│ └─▶ scripts/quality-gate.sh │
│ ├─▶ Unit Tests │
│ ├─▶ Lint │
│ ├─▶ Type Check │
│ ├─▶ Build │
│ └─▶ E2E Tests │
│ │ │
│ ├─── FAIL ──▶ Back to Step 2 │
│ │ │
│ ▼ │
│ 5. COMMIT │
│ └─▶ git add . && git commit -m "Phase complete" │
│ └─▶ git push │
│ └─▶ bd close $ISSUE_ID │
│ │ │
│ ▼ │
│ 6. NEXT PHASE ──────┴──▶ Repeat from Step 2 │
│ │
└─────────────────────────────────────────────────────────────────────┘
| Command | Description |
|---|---|
/auto-tdd-start | Initialize project with Beads issues from plan |
/auto-tdd-run | Execute current phase with TDD + E2E |
/auto-tdd-e2e | Run E2E tests with Playwright agents |
/auto-tdd-status | Show progress and remaining phases |
# 1. Ralph Wiggum plugin
/plugin install ralph-wiggum@anthropics
# 2. Beads CLI
npm install -g @beads/bd
bd init
# 3. Playwright (for E2E)
npm install -D @playwright/test
npx playwright install
# 1. Create plan document
# Use feature-planner skill or create .doc/plans/PLAN_<feature>.md
# 2. Initialize beads issues
/auto-tdd-start
# 3. Execute phases (repeat until done)
/auto-tdd-run
# 4. Check status
/auto-tdd-status
specs/test.plan.mdtests/<suite>/<test>.spec.tsLaunch 3 Task tools in parallel:
1. subagent_type="playwright-test-generator" (Auth tests)
2. subagent_type="playwright-test-generator" (User tests)
3. subagent_type="playwright-test-generator" (API tests)
# Run all checks
./scripts/quality-gate.sh
# With options
./scripts/quality-gate.sh --verbose --skip-e2e
Returns:
/ralph-loop "
═══ PHASE: [Title] ═══
Issue: [ISSUE_ID]
CONTEXT: bd show [ISSUE_ID]
TDD:
🔴 RED: Write tests → npm test → Expect FAIL
🟢 GREEN: Implement → npm test → Expect PASS
🔵 REFACTOR: Clean → npm test → Confirm PASS
QUALITY GATE:
npm test && npm run lint && npm run type-check && npm run build
ON PASS:
git add . && git commit -m 'Complete: [Title]'
bd close [ISSUE_ID]
<promise>PHASE_COMPLETE</promise>
" --max-iterations 50 --completion-promise "PHASE_COMPLETE"
# Create phase issue
bd create "Phase 1: Core Models" -t task -p 1
# Set dependencies
bd dep add <phase2> <phase1> --type blocks
# Update progress
bd update <id> --notes "Progress: 50%"
# Close on completion
bd close <id> --reason "Quality gate passed"
# Check what's ready
bd ready
project/
├── .beads/ # Beads database
├── docs/plans/ # Plan documents
│ └── PLAN_<feature>.md
├── specs/ # E2E test plans
│ └── test.plan.md
├── tests/ # E2E test files
│ ├── seed.spec.ts
│ └── <suite>/
│ └── <test>.spec.ts
├── src/ # Implementation
└── scripts/
└── quality-gate.sh # Quality gate automation
--completion-promise matches exactly--max-iterationsplaywright-test-healer agentnpm run dev)bd show <id>./scripts/quality-gate.sh --verboseThis skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.