task-to-code

To implement coding tasks without scope drift, apply prepared changes from an existing coding-task document strictly, enforcing guardrails and running defined verification steps to ensure exact adherence.

The best way to enforce strict adherence is to apply prepared coding changes from a known task name and coding-task index, preventing scope drift by re-checking current code and running defined verification steps.

To run verification steps for a prepared code change, apply the documented changes from the coding-task document and execute the specific verification steps defined for that coding task to ensure correctness.

You do not strictly need an implementation plan, but when an implementation-plan document is present, the workflow reads it alongside the coding-task document to apply the prepared changes exactly as documented.

Coding task implementation adds unintended scope when strict adherence to the prepared changes is not enforced; applying guardrails and re-checking current code against the coding-task document prevents this drift.

Yes, you can use this workflow to re-check current code before applying changes; it reads the coding-task document, re-checks the existing codebase state, and applies the prepared changes without adding scope.