mvt-implement

To implement production code from an approved architecture design, use a design-driven workflow that converts change-tracking guidance into an ordered implementation plan before modifying files. This ensures code changes follow dependency order and comply with module boundaries.

Preventing scope drift during feature development requires boundary control mechanisms that detect when work exceeds the active task, introduces new public APIs, or structurally deviates from the approved design. This keeps implementation strictly aligned with the original architecture.

Managing dependency-ordered file changes in multi-project repositories involves applying plan-driven tasks that sequence modifications according to architectural dependencies. This approach interface-bounds changes and preserves module boundaries across the repository structure.

Yes, you can generate implementation artifacts for downstream review and testing. The workflow verifies design alignment, records any deviations, and writes an implementation artifact that supports plan-aware deliverables for subsequent testing phases.

Yes, an approved change design is required before starting code implementation. This Skill specifically applies to feature development workflows where requirements and design already exist, serving as a disciplined path from blueprint to code.

Design compliance matters for interface-bound changes because it enforces layer rules and prevents ad hoc architecture modifications during implementation. Verifying design alignment ensures the final production code strictly adheres to the approved technical requirements.