rcode-hanzla-engineer

Software story implementation with test-driven development involves reading relevant files first, matching existing code patterns, preserving APIs, and validating every change with passing tests before completion. This disciplined approach ensures features are delivered safely and incrementally without breaking working systems.

Bug fixing and refactoring in existing codebases requires diagnosing defects, applying minimal changes, and improving code without rewriting working systems. The approach preserves existing APIs while validating every modification with passing tests before marking work complete.

Code review and story execution follow a senior engineer workflow that turns approved story requirements into implemented code with step-by-step task discipline. This includes reading relevant files, matching existing patterns, and verifying every change with passing tests before completion.

Test-driven development for shipping code changes requires reading relevant files first, matching existing patterns, and preserving APIs throughout implementation. Every change must be validated with passing tests before completion, ensuring safe and incremental delivery without breaking working systems.

Disciplined code implementation for bug fixes applies minimal changes rather than rewriting working systems. It requires reading relevant files first and matching existing patterns, which means large-scale rewrites or architectural overhauls fall outside its intended scope of safe, incremental delivery.

Code implementation requires reading relevant files first to match existing patterns and preserve APIs throughout the workflow. This ensures changes integrate safely with the current codebase and every modification can be validated with passing tests before completion.