ki-implementlisted

# ki-implement **Kind:** process. Delivers one approved, ready work record to an evidence-backed awaiting-review boundary. Read [the implementation procedure](references/standards-implementation.md) and [the local authority notes](references/sources.md) before acting. ## What this skill does `ki-implement` owns one work record's delivery path from `ready` to `in-progress` to `awaiting-review`. It does not choose work, create or reshape a plan, close a lifecycle, or delete a record. 1. Resolve the repository's selected adapter, then preflight its exact canonical record, readiness, approval, dependencies, and stated verification. Stop before execution when that adapter is remote pending `KI-HARNESS-FND-014`. 2. Record immutable baseline evidence and transition only that record to `in-progress`. 3. Apply the approved plan within its boundary. 4. When `ki-delegation` is active in the same scope, apply its suitability test and coordinator-first contract. For suitable substantial work, keep the primary agent available as coordinator while bounded subagents execute the approved worker lanes; otherwise continue locally. Create or confirm the durable packet before spawning workers. 5. Review and integrate bounded results, run the required verification, and record the evidence. 6. Create the roadmap-owned required review packet—`Delivered`, `Summary of changes`, `Verification`, `Outstanding concerns`, `Post-change review`, then `Mini recap`—transition the record to `awaiting-rev