implement-issuelisted

# Implement an issue from its plan ## What this does `create-issue` builds every issue around a `**🛠️ Implementation plan**` section: a checklist of `### Task N` blocks whose every step is a `- [ ]` checkbox, with the **last step of each task being its commit message**. (Older issues carry the same plan as a comment — this skill handles both.) That plan is a contract an executor can run cold; this skill is that executor. It turns the plan into a real PR the way a careful engineer would: isolated worktree, draft PR opened up front so progress is visible, one commit per task, and — the part that makes the issue a live progress board — **each task's checkboxes get ticked on the issue as the work lands.** When the last box is checked, it runs a code review, fixes what surfaces, and marks the PR ready. Plans name this skill as their executor (the header note in [`../_shared/plan-shape.md`](../_shared/plan-shape.md)), and the doctrine it executes by — the plan shape, the TDD loop in [`../_shared/tdd-loop.md`](../_shared/tdd-loop.md) — ships under `skills/_shared/`, so it runs the same on every machine with no third-party plugin installed (#324). This skill owns the GitHub/worktree/PR bookkeeping around that doctrine. ## Autonomy contract Run **hands-off** once started — the user watches, doesn't babysit. See [ADR 0005](../../docs/adr/0005-the-lifecycle-skills-run-hands-off-triage-backlog-does-not.md) for the decision scope. Whenever a step (a dispatched sub-agent, the code-r