Plan to Code

Stage 3 of 4. Consumes a plan and one task number. Produces code, one commit, and ticked checkboxes. Runs once per task, in its own session.

Announce at start: "Using plan-to-code to implement Task N of this plan, and only Task N."

The whole point of this skill is that it stops. It stops before verifying, because the user verifies. It stops at the task boundary, because the next task gets a fresh session. Momentum past either of those points is the failure mode this design exists to prevent.

1. Take the arguments

You need a plan path and a task number. Never choose a task yourself.

If the task number is missing, read the plan, then print exactly and stop:

No task number was given, so I have not started anything.