tk-implement

Ready ticket implementation

explicitly /tk-implement or $tk-implement only when is selected. After confirming the repository root of the current checkout as git rev-parse --show-toplevel, <repository-root>/.tigerkit/tickets.md read exactly one Status: Ready ticket and <repository-root>/.tigerkit/implement.md the instructions in . If there is no input or the document is missing, stop with Status: Unverifiable . Pending, stale state, lineage mismatch, unresolved model/effort each stop with exactly Status: Blocked and do not create changes, staging, commit, or receipt.

Procedure

1. Verify that the ticket's latest lineage, exact owned paths, Scope, R/AC, Verification, and symbolized model 과 effort are all resolved. delegated If the execution is modeldecide before worker creation, and validate the optional .tigerkit/session.md's per-host routing with skills/tk-drive/references/worker-dispatch.md#session-model-routing's defined schema to prepare the general-purpose implementer's brief/report paths. If routing is absent or incomplete, propose the exact Markdown addition of model/effortper nested class and routing_state=decision-required, and stop with Status: Pending. The approval screen must include the model class, selector, effort level, and routing source. Before implementation, snapshot the existence and bytes of git status --porcelain=v1과 .tigerkit/implement.md, preserve the existing bytes of user changes, the index, and existing receipts byte-for-byte, and append only after a successful commit. Read only outside owned paths.
2. For a limited low-risk standalone task, recommend direct, and if risk, scope, isolation, or new context is needed, use delegated. delegatedIf is required, do not silently substitute with direct. For any delegated execution, if a required worker cannot be dispatched, terminate with exactly Status: Blocked and do not create or modify changes, staging, commit, or receipt. general-purpose The label is the intended worker role, and do not retroactively determine model/tier from the returned label. directuses focused inspection and self-review without a subagent. delegated는 새 general-purpose reviewer가 Spec compliance와 Task qualityDo not treat a commit as successful before confirming .
3. The implementer modifies only the exact owned paths and runs focused inspection first.
4. delegated Only when or user/repository policy requires independent review does a reviewer with capability at or above implementer inspect Spec/AC 및 Standards/Style . In all direct executions, do not create this reviewer. Verbatim or style mismatch is Blocking .
5. If a gap appears in verification or review, fix it each time with a new corrective worker limited in scope and verify again. If it fails, terminate with Status: Fail/Blocked and do not create staging, commit, or a success receipt.
6. Only when all required verification and review succeed, the current branchcreate exactly one commit in , and after that implement.md에 unit/ticket, changed paths, check/review/gap evidence, commit/ancestry, delegated model_class/requested_selector/realized_model/ reasoning_effort/worker_id/receipt_source, unresolved: none append the receipt. If the host does not expose the realized model, set it to unavailable. Pushing, publishing, and calling other workflows/skills are prohibited.

The output only briefly reports the absolute path of the receipt and Status: Pass/Status: Pending/Status: Blocked/Status: Fail/Status: Unverifiable. Do not copy the evidence inside the receipt into the chat.