implementation-phase

Implement features using Test-Driven Development by writing tests first, then coding to pass them through RED-GREEN-REFACTOR cycles. Prevent code duplication by running anti-duplication checks to detect and refactor duplicate logic before coding new features.

The RED-GREEN-REFACTOR cycle in TDD-driven implementation is a disciplined task triplet where you write failing tests first, implement code to pass them, and then refactor. It enforces continuous testing and quality during feature integration.

Yes, you must load tech stack constraints from docs/project/tech-stack.md before running automated tests. Loading these constraints ensures type safety, validates security patterns, and maintains test coverage aligned with your project requirements.

The best way to maintain traceability during implementation is updating NOTES.md and state indicators after task completion. Track task dependencies in tasks.md and commit implementations with descriptive messages to ensure continuous documentation.

You should run anti-duplication checks before writing new code to detect and refactor existing duplicate logic. This prevents code duplication, enforces quality assurance, and ensures continuous testing standards are met during feature integration.

Yes, you can generate test suites for complex features using test-architect before executing TDD implementation. Review task dependencies in tasks.md first, then generate suites to support the RED-GREEN-REFACTOR cycles effectively.