developer-specialist

Use TDD to design and implement features by applying the RED→GREEN→REFACTOR cycle, which translates a product brief into a disciplined, minimal-change plan with explicit responsibility boundaries and small, test-driven iterations.

Diff-driven development produces small, review-friendly changes with explicit rationale and traceability, ensuring each iteration remains minimal and free from duplicated responsibilities for faster, clearer code reviews.

Prevent design bleed during refactoring by enforcing clear responsibility boundaries and avoiding duplication, refraining from provisional compromises to keep changes precise and isolated within the system's existing architecture.

Translate a product brief into a test-first implementation plan by outlining responsibilities, writing a failing test, implementing minimal code to pass, and refactoring for clarity through the RED→GREEN→REFACTOR cycle.

Yes, you need clear inputs about responsibilities, tests, and boundaries before starting, as the implementation requires explicit responsibility boundaries to prevent design bleed and ensure minimal, reviewable changes.

Avoid minimal-change TDD when inputs about responsibilities, tests, and boundaries are unclear, as the approach requires a well-defined product brief to produce a concrete, step-by-step plan for implementation and verification.