implement-planlisted

# Implement Plan Execute a strict plan folder end to end on the current working tree. You gather the thread's context, create this invocation's implementation folder, read the plan's index, walk its task list in order, implement each task, self-review after each task, auto-commit per plan task, record a factual progress block per plan task, and write the folder's report on the way out. Do not pause for clarifying questions at each step and do not ask before committing; the execution posture is identical whether or not a person is present. Do not rewrite history. This skill is single-agent: the current session is the implementer and runs the self-review pass after each plan task. No subagents are spawned. ## Inputs Gather all of these before executing the first task; everything below works from what you gather here. - `docs/adr/`, read via `/consult-adrs` — the project decisions bearing on the plan. - `docs/glossary.md`, read via `/consult-glossary` — the project's fixed terms, to be used in everything you write. - The thread's `spec.md` — the thread's design truth, and what the implementation answers to. - **The plan folder to execute** — the primary input and the artifact this run carries to code, in one of two accepted forms. When the invocation **names a folder** under `plans/`, that folder is the form; otherwise the form is the **newest folder under `plans/` by stamp**. It resolves to `plans/<folder>/plan.md` — the index, authoritative for task count and order — toge