implementlisted

# Implement Execute an input end-to-end on the current working tree. You gather the thread's context, create this invocation's implementation folder, derive implicit tasks if the input does not already enumerate them, implement each task, self-review, auto-commit per implicit task or per explicit Git instruction the user passes through, record a factual progress block per implicit 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 implicit task. No subagents are spawned. ## Inputs Gather all of these before deriving implicit tasks; everything below works from what you gather here. - `docs/adr/`, read via `/consult-adrs` — the project decisions bearing on the implementation. - `docs/glossary.md`, read via `/consult-glossary` — the project's fixed terms, to be used in everything you write. - The thread's `spec.md`, when the file exists — the thread's design truth, and what the implementation answers to. - The thread's `seed.md` — why the thread exists and what triggered it. - The thread's `adr/` and `glossary.md` — the thread's delta of the project layer, which inside the thread takes precedence over the project records. - **The work to carry to code** — the primary input, in one of two ac