Test-Driven Development (TDD) red-green-refactor cycle for GMailArchiver. Use when implementing features, fixing bugs, or following the 6-phase workflow. Triggers on: TDD, test-driven, red-green, failing test, write test first, implement feature, fix bug, development workflow, phase.
Scanned 9/8/2026
Install to Claude Code
npx -y skills add mattnigh/skills_collection --skill collection --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Collection?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/mattnigh-collection-e8dd5287)More formats (shields.io, HTML) on the badges page.
---
name: tdd-workflow
description: >-
Test-Driven Development (TDD) red-green-refactor cycle for GMailArchiver.
Use when implementing features, fixing bugs, or following the 6-phase workflow.
Triggers on: TDD, test-driven, red-green, failing test, write test first,
implement feature, fix bug, development workflow, phase.
---
# TDD Workflow for GMailArchiver
This skill provides guidance on the Test-Driven Development process.
## Source Documentation
**Always read the authoritative source:**
**`docs/PROCESS.md`** - Development workflow containing:
- Phase 3: Test (TDD Red) - Writing failing tests first
- Phase 4: Code (TDD Green) - Making tests pass with minimal code
- Red-green-refactor cycle explanation
- Exit criteria for each phase
- Definition of done
## Red-Green-Refactor Cycle
1. **Red**: Write a failing test
- Test describes expected behavior
- Verify test actually fails
2. **Green**: Write minimal code to pass
- Simplest solution that works
- Don't over-engineer
3. **Refactor**: Improve code quality
- Remove duplication
- Improve naming
- Verify tests still pass
## Related Skills
- **testing-guidelines** - For test patterns and fixtures (docs/TESTING.md)
- **coding-standards** - For code style (docs/CODING.md)
## Usage
When following TDD:
1. Read `docs/PROCESS.md` Phase 3 and 4 for the workflow
2. Use `/test` command for Phase 3 guidance
3. Use `/code` command for Phase 4 guidance
4. If process changes, update `docs/PROCESS.md` (not this skill)
The source documentation is the **single source of truth** - this skill just points you there.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!