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, append typed entries to the run progress file as the run proceeds, 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.

• 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 implementation.
• 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, when the file exists — 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.
• The thread's seed.md — why the thread exists and what triggered it.
• The work to carry to code — the primary input, in one of two accepted forms. When the invocation points at a plan folder under plans/, that folder is the form: the folder it names, or the newest folder under plans/ by stamp when it points at plans/ without naming one. Read its plan.md, whose ordered steps are what the run executes, together with the brief each step indexes under plan-tasks/ when the folder holds them — a brief carries its step's files, verification, and acceptance criteria. Otherwise the form is a referenced artifact or the user's prompt: a repository path, a directory, a git ref, a GitHub issue (full URL or the short owner/repo#NNN form), or the user's prompt itself when nothing else is named; the run derives its implicit tasks from it either way.
• Every implementations/*/report.md whose Plan: line names the same plan folder, when present — its ## Changes task ledger is the record of what earlier passes over that plan already delivered, and the only source this run resumes from across invocations; a task a ledger records as completed is skipped once it is verified against the code.