What problem does it solve? Teams lose track of project knowledge when facts are duplicated across documents, written without review, or forced into a structure that does not match the project's own conventions. This Skill enforces a disciplined lifecycle for how facts enter and live in a project's knowledge base. ## Core Features & Use Cases - One-fact-one-home placement: Every fact lives in exactly one file, placed according to the project's own KB structure (never an imposed taxonomy), with other documents linking to it. - Direct-write + review-flip lifecycle: Agent-derived facts are written once with Status: Pending review, then flipped to Confirmed after human review; developer-stated facts are written directly as Confirmed. - Index and commit discipline: KB index files are updated on every add/rename/status change, and files are committed to git only when they become Confirmed. - Use Case: After code recon reveals that the billing module retries failed payments three times, write that fact into the module's KB doc marked Pending review, link it from the index, and tell the developer exactly which file to confirm. ## Quick Start Use the context-writing skill to record this newly discovered fact in the project's knowledge base following its existing structure and status conventions.
