task-implementer

To automate a pre-planned refactoring task group without breaking code, execute targeted TK-NNN tasks using a behavior-preservation contract. This approach reads and modifies only files listed in the plan, ensuring deterministic execution and strict task isolation.

Strict task isolation in code modification restricts changes to only the files specified within a pre-planned task group. You need it when executing deterministic refactoring to prevent unintended side effects and preserve all existing interfaces.

To execute deterministic code modification for targeted TK-NNN sub-tasks, provide the specific sub-tasks in your message. The execution applies them in the exact order specified by the plan, using the system prompt as the behavior-preservation contract.

Yes, behavior-preservation contract refactoring supports automated task execution by relying on a completed plan. It integrates with a task iterator tool to coordinate task groups, ensuring operators do not need to re-analyze the codebase during execution.

No, you cannot modify files outside the plan during automated refactoring task execution. The strict task isolation mechanism ensures it reads and modifies only the files listed in the plan, preserving all interfaces and avoiding non-planned changes.

Interface preservation matters when running automated refactoring tasks because it prevents non-planned changes to the system prompt contract. This guarantees that deterministic execution maintains existing software behavior while applying only the specified code modifications.