Help us improve
Share bugs, ideas, or general feedback.
From aura-frog
Writes failing test scaffolding (TDD RED phase) from Phase 1 requirements, verifies all tests fail, generates test-to-requirement mapping and remaining phase estimations.
npx claudepluginhub nguyenthienthanh/aura-frog --plugin aura-frogHow this command is triggered — by the user, by Claude, or both
Slash command
/aura-frog:phase-2workflow/The summary Claude sees in its command listing — used to decide when to auto-load this command
# Command: workflow:phase:2 **Purpose:** Execute Phase 2 - Test RED (Write Failing Tests) **Trigger:** Auto-triggered after Phase 1 approval OR manual `/workflow:phase:2` --- ## 🎯 Phase 2 Objectives Write failing tests before implementation (TDD RED phase). All tests must fail at this stage - they define the expected behavior for Phase 3. **Deliverables:** 1. Test scaffolding with failing tests 2. Test cases covering requirements from Phase 1 3. Verification that all tests fail (RED state) --- ## 📋 Execution Steps ### Step 1: Pre-Phase Hook - Load Phase 1 requirements and design -...
/tdd-redGenerates comprehensive failing tests for a feature following TDD red phase rules. Verifies all tests fail correctly, provides run commands, coverage metrics, and green phase next steps.
/vcsdd-tddGenerates failing test cases for all VCSDD feature spec requirements (Red phase), runs to verify failures and regression baseline passes, records evidence log.
/tdd-redExecutes the TDD Red phase by creating failing test cases based on requirements and task notes. Validates tests fail before proceeding, then records results and updates documentation.
Share bugs, ideas, or general feedback.
Purpose: Execute Phase 2 - Test RED (Write Failing Tests)
Trigger: Auto-triggered after Phase 1 approval OR manual /workflow:phase:2
Write failing tests before implementation (TDD RED phase). All tests must fail at this stage - they define the expected behavior for Phase 3.
Deliverables:
Primary Agent: tester
Actions:
Agent: tester + Dev agent
Create:
# Phase 2: Test RED - Deliverables
## Test Cases
| ID | Requirement | Test Type | Status |
|----|------------|-----------|--------|
| T1 | [req] | unit | RED ✗ |
| T2 | [req] | integration | RED ✗ |
## Test Files Created
- tests/unit/[component].test.ts
- tests/integration/[feature].test.ts
## Estimation
### Story Points
**Total:** X story points (Fibonacci scale)
**Breakdown:**
- Phase 2 (Test RED): 2 points
- Phase 3 (Build GREEN): 5 points
- Phase 4 (Refactor + Review): 3 points
- Phase 5 (Finalize): 1 point
**Confidence:** High/Medium/Low
### Time Estimate
- Phase 2-5: X hours
- **Total:** Z hours (~W days)
Phase 2 is complete when:
Phase 2 auto-continues to Phase 3 (Build GREEN) without approval gate. The failing tests serve as the specification for implementation.
═══════════════════════════════════════════════════════════
🔴 PHASE 2 COMPLETE: Test RED
═══════════════════════════════════════════════════════════
📊 Summary:
Test scaffolding created - all tests failing (RED)
📦 Deliverables:
📄 Test files with failing tests
📊 Test-to-requirement mapping
📈 Metrics:
- Test files created: X
- Test cases: Y (all RED ✗)
- Coverage target: Z%
⏭️ AUTO-CONTINUING to Phase 3: Build GREEN 🟢
═══════════════════════════════════════════════════════════
logs/contexts/{workflow-id}/deliverables/
└── PHASE_2_TEST_RED.md (test cases and scaffolding report)
After Phase 2 completes:
/workflow:phase:3 - Build GREEN (implement code to make tests pass)docs/phases/PHASE_2_TEST_RED.MDcommands/workflow/phase-2-test.mdcommands/workflow/phase-1.mdcommands/workflow/phase-3.mdcommands/workflow/start.mdStatus: Active command Related: workflow:phase:1, workflow:phase:3, workflow:approve