DO

To execute a software implementation plan exactly as specified, load the active plan into the context and instruct the system to apply changes without altering interfaces, ensuring strict adherence to existing code conventions.

Ensuring backward compatibility during automated code changes requires enforcing strict error handling, resource management, and breaking-change safeguards across affected layers like firmware, backend, and frontend without altering existing interfaces.

Context-driven code implementation determines impacted components by analyzing the active plan to select relevant areas, identifying affected layers like Docker and agents, and applying changes using established skill patterns.

Yes, you can automate plan execution across firmware, backend, frontend, and Docker layers by coordinating with relevant layers from the loaded context and applying changes through existing skill patterns without interface alterations.

Automated code execution mitigates breaking changes by enforcing robust safety compliance and backward compatibility, but it strictly requires adherence to existing code conventions and relies on the active plan context to determine impacted components.

Context loading fails when the active plan is not properly provided in the context, preventing the system from determining impacted components and identifying required skills and rules for accurate code implementation.