Implement

Execute approved work from a setup-project backlog without changing scope or priority. A standalone WORK-NNN is one acceptance unit. An EPIC-NNN and all approved children are one outcome acceptance unit: children remain provisional until the composed Epic is reviewed, verified, merged, reconciled, completed, and archived.

Use one conventional branch per acceptance unit and allow no other local non-primary branch. Epic children never integrate to primary, publish wiki state, or become done independently. An internal provisional-child or provisional-standalone packet from $implement-with-subagents executes one serial delta on that branch without review, governance, or acceptance gates.

Authority And Approval

The item's outcome, acceptance criteria, exclusions, and approved relationships define implementation scope. Its parent Epic supplies coordination context but never expands child scope. The accepted wiki and repository instructions define the current-state baseline and engineering constraints.

The invocation is a gate-backed execution workflow: it authorizes temporary claims, checklist evidence, and normal execution status transitions for the selected approved scope — not changes to outcome or acceptance wording, rank, parentage, relationships, cancellation, child scope, or accepted wiki knowledge. Preserve proposed cancellation and out-of-scope decisions in the backlog and stop for owner approval. Obtain explicit approval for the exact durable wiki update unless already explicitly approved.

Under $to-product, its autonomous contract supplies every user-authorizable decision required by the PRD, including record/Epic reshaping, cancellation, recovery, wiki updates, acceptance, and closure. It never authorizes unrelated or out-of-PRD implementation; file adjacent scope as proposed.

Authority Packet Freshness

An authority — record, index, wiki concept, ADR, guidance page, or source file — read completely during this invocation stays read; re-reading it is waste. A skill invoked from here accepts the packet paths and roles this invocation already resolved instead of rediscovering them. Freshness is per-invocation: never inherit it across invocations, and never assume a subagent holds it.

An already-read authority is void and must be re-read when any of these holds: