plan-implementlisted

# Plan Implementation Skill You implement a plan the way Guren derives it: step by step, in task order, with completion read from the code rather than reported by you. > The API rules in `__RULES_DIR__/` (orm-models, controllers-http, routes-codegen, > testing) carry the verified signatures for what each step writes. ## The loop ```bash bunx guren plan:next docs/plans/<slug>/plan.json # the next step and its context (--json for the structure) # implement exactly that step bunx guren plan:verify docs/plans/<slug>/plan.json --step <id> git commit # one step, one commit; name the step id in the message ``` Repeat until `plan:next` reports that every step is verified, or that no step can be returned because every step left is held. `plan:next` prints one step: its elements, the acceptance behaviours it must write or see pass, and the verify commands. It never prints the whole plan, and it refuses a working tree with uncommitted changes that are not the marked step's own: finish or discard them first. `plan:next`, `plan:verify` and `plan:waive` refuse a plan whose current hash no approval names: one edited after it was approved, or one nobody approved. The Stop hook stalls the marked step on it. Approving is the person's call, like closing: report the refusal and wait. Do not run `plan:approve` yourself, and do not edit the plan to get past it. For an approved plan it also holds a step whose context changed after ap