loop-implement

# loop-implement — the single implementation loop, driven by a wiki-plan Drive work to "done" through a closed, methodology-grounded loop (sources at the bottom). **This is dev-loop's one and only implementation skill** — it both plans (via `wiki-plan`, step 2) and executes, so there is no separate executor. The plan `wiki-plan` produces is not a loose sketch: it fixes an ordered task list and, for each task, *navigates to the exact wiki pages that ground it* (the decision→page map). This loop **consumes that plan directly** — executing the tasks in the plan's order, loading exactly the wiki pages each task names, and citing them — so every change traces back to a verified wiki page. It works the same whether it runs standalone (you produce the plan here in step 2) or as an orchestrated worker (the orchestrator hands you a task brief *and* the plan it already produced, and you adopt and implement it here). Either path, one loop. ## When to use - Use: logic changes, new features, bug fixes, behavior-changing refactors. - Skip: typos, config values, simple rename/import cleanup, one-line edits. ## Two entry modes (both run the SAME loop) - **A plan already exists** (a `plans/<feature>/` from a prior `wiki-plan` run, or handed to you by the orchestrator): skip producing one — execute its tasks in the `## Task order` sequence, one at a time, each through steps 0 and 3–7 below, loading that task's named wiki pages. - **No plan yet** (a fresh standalone task): step 2 runs...