tdd-workflow
GMailArchiver的测试驱动开发(TDD)红-绿-重构周期。在实现功能、修复错误或遵循6阶段工作流时使用。触发条件:TDD、test-driven、red-green、failing test、write test first、implement feature、fix bug、development workflow、phase。
📖 中文导读:GMailArchiver的测试驱动开发(TDD)红-绿-重构周期。在实现功能、修复错误或遵循6阶段工作流时使用。触发条件:TDD、test-driven、red-green、failing test、write test first、implement feature、fix bug、development workflow、phase。 以下正文为该技能的原始 SKILL.md 内容(英文),上方安装命令可直接使用。
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
Red: Write a failing test
- Test describes expected behavior
- Verify test actually fails
Green: Write minimal code to pass
- Simplest solution that works
- Don't over-engineer
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:
- Read
docs/PROCESS.mdPhase 3 and 4 for the workflow - Use
/testcommand for Phase 3 guidance - Use
/codecommand for Phase 4 guidance - 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.