code-implementation

An architecture-aware test-driven workflow plans, implements, and validates code changes end-to-end. It requires upfront planning, mandatory tests, and progressive review gates before merging features, refactors, or bug fixes.

To implement code changes end-to-end, provide a detailed implementation plan, begin coding once approved, execute mandatory tests, and pass progressive review gates before merging. This ensures changes are traceable with clear acceptance criteria and rollback notes.

Yes, this code implementation workflow supports both frontend and backend tasks. It handles multi-domain scope changes with explicit test plans and gating for features, refactors, and bug fixes.

The best way to reduce bug risk is using a disciplined coding workflow that completes planning, testing, and reviews before deployment. This incremental delivery approach ensures changes are traceable with clear acceptance criteria.

Yes, an upfront implementation plan is required before coding starts. The workflow demands a detailed plan with clear acceptance criteria, which must be approved before implementation begins to reduce miscommunication.

A test-driven implementation workflow may not suit rapid prototyping or throwaway scripts. It is designed for structured features, refactors, and bug fixes requiring progressive verification, mandatory tests, and review gates before merge.