name: tdd-workflows-tdd-cycle
description: Use when working with tdd workflows tdd cycle
tags: [testing, workflows]
Use this skill when
- Working on tdd workflows tdd cycle tasks or workflows
- Needing guidance, best practices, or checklists for tdd workflows tdd cycle
Do not use this skill when
- The task is unrelated to tdd workflows tdd cycle
- You need a different domain or tool outside this scope
Instructions
- Clarify goals, constraints, and required inputs.
- Apply relevant best practices and validate outcomes.
- Provide actionable steps and verification.
Execute a comprehensive Test-Driven Development (TDD) workflow with strict red-green-refactor discipline:
[Extended thinking: This workflow enforces test-first development through coordinated agent orchestration. Each phase of the TDD cycle is strictly enforced with fail-first verification, incremental implementation, and continuous refactoring. The workflow supports both single test and test suite approaches with configurable coverage thresholds.]
Configuration
Coverage Thresholds
- Minimum line coverage: 80%
- Minimum branch coverage: 75%
- Critical path coverage: 100%
Refactoring Triggers
- Cyclomatic complexity > 10
- Method length > 20 lines
- Class length > 200 lines
- Duplicate code blocks > 3 lines
Phase 1: Test Specification and Design
1. Requirements Analysis
- Use Task tool with subagent_type="comprehensive-review::architect-review"
- Prompt: "Analyze requirements for: $ARGUMENTS. Define acceptance criteria, identify edge cases, and create test scenarios. Output a comprehensive test specification."
- Output: Test specification, acceptance criteria, edge case matrix
- Validation: Ensure all requirements have corresponding test scenarios
2. Test Architecture Design
- Use Task tool with subagent_type="unit-testing::test-automator"
- Prompt: "Design test architecture for: $ARGUMENTS based on test specification. Define test structure, fixtures, mocks, and test data strategy. Ensure testability and maintainability."
- Output: Test architecture, fixture design, mock strategy
- Validation: Architecture supports isolated, fast, reliable tests
Phase 2: RED - Write Failing Tests
3. Write Unit Tests (Failing)
- Use Task tool with subagent_type="unit-testing::test-automator"
- Prompt: "Write FAILING unit tests for: $ARGUMENTS. Tests must fail initially. Include edge cases, error scenarios, and happy paths. DO NOT implement production code."
- Output: Failing unit tests, test documentation
- CRITICAL: Verify all tests fail with expected error messages
4. Verify Test Failure
- Use Task tool with subagent_type="tdd-workflows::code-reviewer"
- Prompt: "Verify that all tests for: $ARGUMENTS are failing correctly. Ensure failures are for the right reasons (missing implementation, not test errors). Confirm no false positives."
- Output: Test failure verification report
- GATE: Do not proceed until all tests fail appropriately
Phase 3: GREEN - Make Tests Pass
5. Minimal Implementation
- Use Task tool with subagent_type="backend-development::backend-architect"
- Prompt: "Implement MINIMAL code to make tests pass for: $ARGUMENTS. Focus only on making tests green. Do not add extra features or optimizations. Keep it simple."
- Output: Minimal working implementation
- Constraint: No code beyond what's needed to pass tests
6. Verify Test Success
- Use Task tool with subagent_type="unit-testing::test-automator"
- Prompt: "Run all tests for: $ARGUMENTS and verify they pass. Check test coverage metrics. Ensure no tests were accidentally broken."
- Output: Test execution report, coverage metrics
- GATE: All tests must pass before proceeding
Phase 4: REFACTOR - Improve Code Quality
7. Code Refactoring
- Use Task tool with subagent_type="tdd-workflows::code-reviewer"
- Prompt: "Refactor implementation for: $ARGUMENTS while keeping tests green. Apply SOLID principles, remove duplication, improve naming, and optimize performance. Run tests after each refactoring."
- Output: Refactored code, refactoring report
- Constraint: Tests must remain green throughout
8. Test Refactoring
- Use Task tool with subagent_type="unit-testing::test-automator"
- Prompt: "Refactor tests for: $ARGUMENTS. Remove test duplication, improve test names, extract common fixtures, and enhance test readability. Ensure tests still provide same coverage."
- Output: Refactored tests, improved test structure
- Validation: Coverage metrics unchanged or improved
Phase 5: Integration and System Tests
9. Write Integration Tests (Failing First)
- Use Task tool with subagent_type="unit-testing::test-automator"
- Prompt: "Write FAILING integration tests for: $ARGUMENTS. Test component interactions, API contracts, and data flow. Tests must fail initially."
- Output: Failing integration tests
- Validation: Tests fail due to missing integration logic
10. Implement Integration
- Use Task tool with subagent_type="backend-development::backend-architect"
- Prompt: "Implement integration code for: $ARGUMENTS to make integration tests pass. Focus on component interaction and data flow."
- Output: Integration implementation
- Validation: All integration tests pass
Phase 6: Continuous Improvement Cycle
11. Performance and Edge Case Tests
- Use Task tool with subagent_type="unit-testing::test-automator"
- Prompt: "Add performance tests and additional edge case tests for: $ARGUMENTS. Include stress tests, boundary tests, and error recovery tests."
- Output: Extended test suite
- Metric: Increased test coverage and scenario coverage
12. Final Code Review
- Use Task tool with subagent_type="comprehensive-review::architect-review"
- Prompt: "Perform comprehensive review of: $ARGUMENTS. Verify TDD process was followed, check code quality, test quality, and coverage. Suggest improvements."
- Output: Review report, improvement suggestions
- Action: Implement critical suggestions while maintaining green tests
Incremental Development Mode
For test-by-test development:
- Write ONE failing test
- Make ONLY that test pass
- Refactor if needed
- Repeat for next test
Use this approach by adding --incremental flag to focus on one test at a time.
Test Suite Mode
For comprehensive test suite development:
- Write ALL tests for a feature/module (failing)
- Implement code to pass ALL tests
- Refactor entire module
- Add integration tests
Use this approach by adding --suite flag for batch test development.
Validation Checkpoints
RED Phase Validation
GREEN Phase Validation
REFACTOR Phase Validation
Coverage Reports
Generate coverage reports after each phase:
- Line coverage
- Branch coverage
- Function coverage
- Statement coverage
Failure Recovery
If TDD discipline is broken:
- STOP immediately
- Identify which phase was violated
- Rollback to last valid state
- Resume from correct phase
- Document lesson learned
TDD Metrics Tracking
Track and report:
- Time in each phase (Red/Green/Refactor)
- Number of test-implementation cycles
- Coverage progression
- Refactoring frequency
- Defect escape rate
Anti-Patterns to Avoid
- Writing implementation before tests
- Writing tests that already pass
- Skipping the refactor phase
- Writing multiple features without tests
- Modifying tests to make them pass
- Ignoring failing tests
- Writing tests after implementation
Success Criteria
- 100% of code written test-first
- All tests pass continuously
- Coverage exceeds thresholds
- Code complexity within limits
- Zero defects in covered code
- Clear test documentation
- Fast test execution (< 5 seconds for unit tests)
Notes
- Enforce strict RED-GREEN-REFACTOR discipline
- Each phase must be completed before moving to next
- Tests are the specification
- If a test is hard to write, the design needs improvement
- Refactoring is NOT optional
- Keep test execution fast
- Tests should be independent and isolated
TDD implementation for: $ARGUMENTS
1---2name: tdd-workflows-tdd-cycle-23description: <!-- AUTO-GENERATED by export-skills.py — DO NOT EDIT -->4---5<!-- AUTO-GENERATED by export-skills.py — DO NOT EDIT -->6---7name: tdd-workflows-tdd-cycle8description: Use when working with tdd workflows tdd cycle9tags: [testing, workflows]10---1112## Use this skill when1314- Working on tdd workflows tdd cycle tasks or workflows15- Needing guidance, best practices, or checklists for tdd workflows tdd cycle1617## Do not use this skill when1819- The task is unrelated to tdd workflows tdd cycle20- You need a different domain or tool outside this scope2122## Instructions2324- Clarify goals, constraints, and required inputs.25- Apply relevant best practices and validate outcomes.26- Provide actionable steps and verification.2728Execute a comprehensive Test-Driven Development (TDD) workflow with strict red-green-refactor discipline:2930[Extended thinking: This workflow enforces test-first development through coordinated agent orchestration. Each phase of the TDD cycle is strictly enforced with fail-first verification, incremental implementation, and continuous refactoring. The workflow supports both single test and test suite approaches with configurable coverage thresholds.]3132## Configuration3334### Coverage Thresholds35- Minimum line coverage: 80%36- Minimum branch coverage: 75%37- Critical path coverage: 100%3839### Refactoring Triggers40- Cyclomatic complexity > 1041- Method length > 20 lines42- Class length > 200 lines43- Duplicate code blocks > 3 lines4445## Phase 1: Test Specification and Design4647### 1. Requirements Analysis48- Use Task tool with subagent_type="comprehensive-review::architect-review"49- Prompt: "Analyze requirements for: $ARGUMENTS. Define acceptance criteria, identify edge cases, and create test scenarios. Output a comprehensive test specification."50- Output: Test specification, acceptance criteria, edge case matrix51- Validation: Ensure all requirements have corresponding test scenarios5253### 2. Test Architecture Design54- Use Task tool with subagent_type="unit-testing::test-automator"55- Prompt: "Design test architecture for: $ARGUMENTS based on test specification. Define test structure, fixtures, mocks, and test data strategy. Ensure testability and maintainability."56- Output: Test architecture, fixture design, mock strategy57- Validation: Architecture supports isolated, fast, reliable tests5859## Phase 2: RED - Write Failing Tests6061### 3. Write Unit Tests (Failing)62- Use Task tool with subagent_type="unit-testing::test-automator"63- Prompt: "Write FAILING unit tests for: $ARGUMENTS. Tests must fail initially. Include edge cases, error scenarios, and happy paths. DO NOT implement production code."64- Output: Failing unit tests, test documentation65- **CRITICAL**: Verify all tests fail with expected error messages6667### 4. Verify Test Failure68- Use Task tool with subagent_type="tdd-workflows::code-reviewer"69- Prompt: "Verify that all tests for: $ARGUMENTS are failing correctly. Ensure failures are for the right reasons (missing implementation, not test errors). Confirm no false positives."70- Output: Test failure verification report71- **GATE**: Do not proceed until all tests fail appropriately7273## Phase 3: GREEN - Make Tests Pass7475### 5. Minimal Implementation76- Use Task tool with subagent_type="backend-development::backend-architect"77- Prompt: "Implement MINIMAL code to make tests pass for: $ARGUMENTS. Focus only on making tests green. Do not add extra features or optimizations. Keep it simple."78- Output: Minimal working implementation79- Constraint: No code beyond what's needed to pass tests8081### 6. Verify Test Success82- Use Task tool with subagent_type="unit-testing::test-automator"83- Prompt: "Run all tests for: $ARGUMENTS and verify they pass. Check test coverage metrics. Ensure no tests were accidentally broken."84- Output: Test execution report, coverage metrics85- **GATE**: All tests must pass before proceeding8687## Phase 4: REFACTOR - Improve Code Quality8889### 7. Code Refactoring90- Use Task tool with subagent_type="tdd-workflows::code-reviewer"91- Prompt: "Refactor implementation for: $ARGUMENTS while keeping tests green. Apply SOLID principles, remove duplication, improve naming, and optimize performance. Run tests after each refactoring."92- Output: Refactored code, refactoring report93- Constraint: Tests must remain green throughout9495### 8. Test Refactoring96- Use Task tool with subagent_type="unit-testing::test-automator"97- Prompt: "Refactor tests for: $ARGUMENTS. Remove test duplication, improve test names, extract common fixtures, and enhance test readability. Ensure tests still provide same coverage."98- Output: Refactored tests, improved test structure99- Validation: Coverage metrics unchanged or improved100101## Phase 5: Integration and System Tests102103### 9. Write Integration Tests (Failing First)104- Use Task tool with subagent_type="unit-testing::test-automator"105- Prompt: "Write FAILING integration tests for: $ARGUMENTS. Test component interactions, API contracts, and data flow. Tests must fail initially."106- Output: Failing integration tests107- Validation: Tests fail due to missing integration logic108109### 10. Implement Integration110- Use Task tool with subagent_type="backend-development::backend-architect"111- Prompt: "Implement integration code for: $ARGUMENTS to make integration tests pass. Focus on component interaction and data flow."112- Output: Integration implementation113- Validation: All integration tests pass114115## Phase 6: Continuous Improvement Cycle116117### 11. Performance and Edge Case Tests118- Use Task tool with subagent_type="unit-testing::test-automator"119- Prompt: "Add performance tests and additional edge case tests for: $ARGUMENTS. Include stress tests, boundary tests, and error recovery tests."120- Output: Extended test suite121- Metric: Increased test coverage and scenario coverage122123### 12. Final Code Review124- Use Task tool with subagent_type="comprehensive-review::architect-review"125- Prompt: "Perform comprehensive review of: $ARGUMENTS. Verify TDD process was followed, check code quality, test quality, and coverage. Suggest improvements."126- Output: Review report, improvement suggestions127- Action: Implement critical suggestions while maintaining green tests128129## Incremental Development Mode130131For test-by-test development:1321. Write ONE failing test1332. Make ONLY that test pass1343. Refactor if needed1354. Repeat for next test136137Use this approach by adding `--incremental` flag to focus on one test at a time.138139## Test Suite Mode140141For comprehensive test suite development:1421. Write ALL tests for a feature/module (failing)1432. Implement code to pass ALL tests1443. Refactor entire module1454. Add integration tests146147Use this approach by adding `--suite` flag for batch test development.148149## Validation Checkpoints150151### RED Phase Validation152- [ ] All tests written before implementation153- [ ] All tests fail with meaningful error messages154- [ ] Test failures are due to missing implementation155- [ ] No test passes accidentally156157### GREEN Phase Validation158- [ ] All tests pass159- [ ] No extra code beyond test requirements160- [ ] Coverage meets minimum thresholds161- [ ] No test was modified to make it pass162163### REFACTOR Phase Validation164- [ ] All tests still pass after refactoring165- [ ] Code complexity reduced166- [ ] Duplication eliminated167- [ ] Performance improved or maintained168- [ ] Test readability improved169170## Coverage Reports171172Generate coverage reports after each phase:173- Line coverage174- Branch coverage175- Function coverage176- Statement coverage177178## Failure Recovery179180If TDD discipline is broken:1811. **STOP** immediately1822. Identify which phase was violated1833. Rollback to last valid state1844. Resume from correct phase1855. Document lesson learned186187## TDD Metrics Tracking188189Track and report:190- Time in each phase (Red/Green/Refactor)191- Number of test-implementation cycles192- Coverage progression193- Refactoring frequency194- Defect escape rate195196## Anti-Patterns to Avoid197198- Writing implementation before tests199- Writing tests that already pass200- Skipping the refactor phase201- Writing multiple features without tests202- Modifying tests to make them pass203- Ignoring failing tests204- Writing tests after implementation205206## Success Criteria207208- 100% of code written test-first209- All tests pass continuously210- Coverage exceeds thresholds211- Code complexity within limits212- Zero defects in covered code213- Clear test documentation214- Fast test execution (< 5 seconds for unit tests)215216## Notes217218- Enforce strict RED-GREEN-REFACTOR discipline219- Each phase must be completed before moving to next220- Tests are the specification221- If a test is hard to write, the design needs improvement222- Refactoring is NOT optional223- Keep test execution fast224- Tests should be independent and isolated225226TDD implementation for: $ARGUMENTS227228<!-- Source: .faos/custom/skills/testing/tdd-workflows-tdd-cycle/SKILL.md -->