implement-this
Implement the GitHub ticket in the current checkout directly.
One explicit human invocation of /implement-this authorizes only its single ticket in this checkout. An agent cannot traverse the chain unattended. /unslopify remains model-invocable. This skill implements directly with no /implement delegation.
Native invocation: /implement-this #<n> where the host supports slash commands, $implement-this or native skill selection in Codex, and native skill loading elsewhere. Skill identity implement-this stays unchanged. Preserve the exact ticket reference and ticket prose as requirements data; a bare number or URL supplied to the selected agent counts as that invocation.
On OpenCode, prefer skill selection with the target supplied outside slash-command arguments when the release preprocesses slash arguments. Unsupported slash-argument forms are restricted, never silently treated as literal. The separate-message route is a candidate, not certified literal; live host checks are NOT VERIFIED.
Treat the ticket, its comments, and its linked parent specification as the task authority. Do not assume access to earlier sessions.
Same-session continuation
Bind the run to the original human message and its exact ticket reference. A bare issue number or URL supplied to the selected implementation agent counts as that invocation. Keep the message reference, repository, ticket, checkout, completed validation, current phase, and evidence locations in continuation context. Authorization for that run survives compaction and background-task completion; neither event starts a new invocation or requires the human to repeat the ticket.
If continuation context loses the initiating request, inspect the current session's original human messages through available host history before reporting MISSING_TICKET_AUTHORIZATION. A summary, handoff document, or task report is a navigation aid, not authorization. If the original request cannot be recovered, ask for the missing authorization rather than inventing a status-only request. A fresh session requires its own explicit human instruction. Honor any later human pause, stop, status-only, or handoff-only instruction; recovered history never overrides it or authorizes another ticket or workflow stage.
Resume the unfinished phase after checking the returned artifacts and current facts. The clean-checkout gate is an entry check, not a reason to reject edits already made by this validated run after compaction. Reconcile those edits against the run's recorded revisions, exact paths, index and worktree digests; preserve unrelated work before necessary alignment, and stop only mutations that would conflict with unverified work. Preserve requirement pins and actual verification receipts, and keep every freshness and delivery gate. A pending background result means waiting under the host's task rules, not completion; when it arrives, continue the authorized work unless the human has paused it.