name: tdd-workflows-tdd-cycle
description: Use when working with tdd workflows tdd cycle
tags: [testing, workflows]
Platform Note: This skill was designed for multi-agent execution. Perplexity Computer handles orchestration automatically — treat sub-agent instructions as sequential steps to complete thoroughly.
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-33description: <!-- 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> **Platform Note:** This skill was designed for multi-agent execution. Perplexity Computer handles orchestration automatically — treat sub-agent instructions as sequential steps to complete thoroughly.1314## Use this skill when1516- Working on tdd workflows tdd cycle tasks or workflows17- Needing guidance, best practices, or checklists for tdd workflows tdd cycle1819## Do not use this skill when2021- The task is unrelated to tdd workflows tdd cycle22- You need a different domain or tool outside this scope2324## Instructions2526- Clarify goals, constraints, and required inputs.27- Apply relevant best practices and validate outcomes.28- Provide actionable steps and verification.2930Execute a comprehensive Test-Driven Development (TDD) workflow with strict red-green-refactor discipline:3132[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.]3334## Configuration3536### Coverage Thresholds37- Minimum line coverage: 80%38- Minimum branch coverage: 75%39- Critical path coverage: 100%4041### Refactoring Triggers42- Cyclomatic complexity > 1043- Method length > 20 lines44- Class length > 200 lines45- Duplicate code blocks > 3 lines4647## Phase 1: Test Specification and Design4849### 1. Requirements Analysis50- Use Task tool with subagent_type="comprehensive-review::architect-review"51- Prompt: "Analyze requirements for: $ARGUMENTS. Define acceptance criteria, identify edge cases, and create test scenarios. Output a comprehensive test specification."52- Output: Test specification, acceptance criteria, edge case matrix53- Validation: Ensure all requirements have corresponding test scenarios5455### 2. Test Architecture Design56- Use Task tool with subagent_type="unit-testing::test-automator"57- Prompt: "Design test architecture for: $ARGUMENTS based on test specification. Define test structure, fixtures, mocks, and test data strategy. Ensure testability and maintainability."58- Output: Test architecture, fixture design, mock strategy59- Validation: Architecture supports isolated, fast, reliable tests6061## Phase 2: RED - Write Failing Tests6263### 3. Write Unit Tests (Failing)64- Use Task tool with subagent_type="unit-testing::test-automator"65- Prompt: "Write FAILING unit tests for: $ARGUMENTS. Tests must fail initially. Include edge cases, error scenarios, and happy paths. DO NOT implement production code."66- Output: Failing unit tests, test documentation67- **CRITICAL**: Verify all tests fail with expected error messages6869### 4. Verify Test Failure70- Use Task tool with subagent_type="tdd-workflows::code-reviewer"71- 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."72- Output: Test failure verification report73- **GATE**: Do not proceed until all tests fail appropriately7475## Phase 3: GREEN - Make Tests Pass7677### 5. Minimal Implementation78- Use Task tool with subagent_type="backend-development::backend-architect"79- 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."80- Output: Minimal working implementation81- Constraint: No code beyond what's needed to pass tests8283### 6. Verify Test Success84- Use Task tool with subagent_type="unit-testing::test-automator"85- Prompt: "Run all tests for: $ARGUMENTS and verify they pass. Check test coverage metrics. Ensure no tests were accidentally broken."86- Output: Test execution report, coverage metrics87- **GATE**: All tests must pass before proceeding8889## Phase 4: REFACTOR - Improve Code Quality9091### 7. Code Refactoring92- Use Task tool with subagent_type="tdd-workflows::code-reviewer"93- Prompt: "Refactor implementation for: $ARGUMENTS while keeping tests green. Apply SOLID principles, remove duplication, improve naming, and optimize performance. Run tests after each refactoring."94- Output: Refactored code, refactoring report95- Constraint: Tests must remain green throughout9697### 8. Test Refactoring98- Use Task tool with subagent_type="unit-testing::test-automator"99- Prompt: "Refactor tests for: $ARGUMENTS. Remove test duplication, improve test names, extract common fixtures, and enhance test readability. Ensure tests still provide same coverage."100- Output: Refactored tests, improved test structure101- Validation: Coverage metrics unchanged or improved102103## Phase 5: Integration and System Tests104105### 9. Write Integration Tests (Failing First)106- Use Task tool with subagent_type="unit-testing::test-automator"107- Prompt: "Write FAILING integration tests for: $ARGUMENTS. Test component interactions, API contracts, and data flow. Tests must fail initially."108- Output: Failing integration tests109- Validation: Tests fail due to missing integration logic110111### 10. Implement Integration112- Use Task tool with subagent_type="backend-development::backend-architect"113- Prompt: "Implement integration code for: $ARGUMENTS to make integration tests pass. Focus on component interaction and data flow."114- Output: Integration implementation115- Validation: All integration tests pass116117## Phase 6: Continuous Improvement Cycle118119### 11. Performance and Edge Case Tests120- Use Task tool with subagent_type="unit-testing::test-automator"121- Prompt: "Add performance tests and additional edge case tests for: $ARGUMENTS. Include stress tests, boundary tests, and error recovery tests."122- Output: Extended test suite123- Metric: Increased test coverage and scenario coverage124125### 12. Final Code Review126- Use Task tool with subagent_type="comprehensive-review::architect-review"127- Prompt: "Perform comprehensive review of: $ARGUMENTS. Verify TDD process was followed, check code quality, test quality, and coverage. Suggest improvements."128- Output: Review report, improvement suggestions129- Action: Implement critical suggestions while maintaining green tests130131## Incremental Development Mode132133For test-by-test development:1341. Write ONE failing test1352. Make ONLY that test pass1363. Refactor if needed1374. Repeat for next test138139Use this approach by adding `--incremental` flag to focus on one test at a time.140141## Test Suite Mode142143For comprehensive test suite development:1441. Write ALL tests for a feature/module (failing)1452. Implement code to pass ALL tests1463. Refactor entire module1474. Add integration tests148149Use this approach by adding `--suite` flag for batch test development.150151## Validation Checkpoints152153### RED Phase Validation154- [ ] All tests written before implementation155- [ ] All tests fail with meaningful error messages156- [ ] Test failures are due to missing implementation157- [ ] No test passes accidentally158159### GREEN Phase Validation160- [ ] All tests pass161- [ ] No extra code beyond test requirements162- [ ] Coverage meets minimum thresholds163- [ ] No test was modified to make it pass164165### REFACTOR Phase Validation166- [ ] All tests still pass after refactoring167- [ ] Code complexity reduced168- [ ] Duplication eliminated169- [ ] Performance improved or maintained170- [ ] Test readability improved171172## Coverage Reports173174Generate coverage reports after each phase:175- Line coverage176- Branch coverage177- Function coverage178- Statement coverage179180## Failure Recovery181182If TDD discipline is broken:1831. **STOP** immediately1842. Identify which phase was violated1853. Rollback to last valid state1864. Resume from correct phase1875. Document lesson learned188189## TDD Metrics Tracking190191Track and report:192- Time in each phase (Red/Green/Refactor)193- Number of test-implementation cycles194- Coverage progression195- Refactoring frequency196- Defect escape rate197198## Anti-Patterns to Avoid199200- Writing implementation before tests201- Writing tests that already pass202- Skipping the refactor phase203- Writing multiple features without tests204- Modifying tests to make them pass205- Ignoring failing tests206- Writing tests after implementation207208## Success Criteria209210- 100% of code written test-first211- All tests pass continuously212- Coverage exceeds thresholds213- Code complexity within limits214- Zero defects in covered code215- Clear test documentation216- Fast test execution (< 5 seconds for unit tests)217218## Notes219220- Enforce strict RED-GREEN-REFACTOR discipline221- Each phase must be completed before moving to next222- Tests are the specification223- If a test is hard to write, the design needs improvement224- Refactoring is NOT optional225- Keep test execution fast226- Tests should be independent and isolated227228TDD implementation for: $ARGUMENTS229230<!-- Source: .faos/custom/skills/testing/tdd-workflows-tdd-cycle/SKILL.md -->