What problem does it solve? Engineering teams lose hard-won context — rejected approaches, gotchas, and design decisions — after every merge, forcing engineers to rediscover what the code alone cannot explain. This Skill maintains a per-repo OKF v0.2 knowledge bundle that assembles one budgeted context block before a run and captures durable facts after each merge. ## Core Features & Use Cases - Budgeted retrieval: retrieve assembles one token-budgeted context block from the epic's root concept via iwe retrieve, with a read-once rule so no fact enters a run twice. - Post-merge capture: capture filters candidate facts, dedupes against existing concepts with iwe find, and writes created/updated/superseded concepts with schema validation before commit and push. - Curation and migration: curate resolves near-duplicate concepts via iwe stats similarity, and migrate moves a client's existing bundle onto the OKF schema with all-or-nothing rollback. - Use Case: After a pull request merges, the post-merge hook runs capture <ticket-id> <merge-sha> to record why an approach was ruled out, so the next ticket's retrieve surfaces that decision instead of the team re-litigating it. ## Quick Start Ask the assistant to run the knowledge retrieve operation for your epic ID to load the bundle's context block before starting a ticket.