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.

• The project's AGENTS.md, when the file exists — the project's standing guidance for agents working in it.
• docs/glossary.md, when the file exists — the project's fixed terms, to be used in everything you write.
• docs/adr/ and docs/pdr/, read via /consult-decisions — the project decisions bearing on the plan.
• The roadmap entry named by the seed frontmatter's roadmap mapping, when the seed carries one — the entry this thread answers: its sketch, its scope boundary and its planned behavior, found as the heading whose text is roadmap.entry in the index at roadmap.path.
• The thread's spec.md — the spec, whose acceptance checklist the implementation answers to.
• The thread's delta/, when present — the thread's delta of the project layer, which inside the thread takes precedence over the project records and holds the decision records, glossary terms and agents-file changes the change lands; a criterion resting on one of its documents cites it by path, and a decision record by stem.
• 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 — together with the plan-tasks/NN-<kebab-slug>.md brief each index entry points at. When the index's Source: line names an artifact other than the thread's spec.md, read that artifact too: it holds the intent the plan was compiled from.
• Every implementations/*/report.md whose Plan: line names that same plan folder — the record of what earlier passes over the plan already delivered; a task one of them records as completed is skipped once it is verified against the code.