okf-wiki

# okf-wiki: scaffold an Open Knowledge Format knowledge base OKF (Open Knowledge Format) stores knowledge as small markdown files: one concept per file, each carrying its own provenance in YAML frontmatter, with directory `index.md` files for navigation and a validator that enforces the contract. It is built for knowledge bases that both people and agents read and edit — newsroom institutional memory, a research atlas, a team's decision log, an infrastructure map. This skill scaffolds a conforming OKF project and validates it. The format contract is in `spec/SPEC.md` (in this skill's directory) — read it before changing structure. ## When to use - The user wants to start an OKF knowledge base, atlas, or wiki. - They want docs structured as one-concept-per-file with provenance, not prose pages. - They want to "initialize OKF" in a repo, optionally publishing into its GitHub wiki. ## Start here: scope the wiki with the user Before you scaffold anything, settle four things with the user. They shape what gets created and how it is published, and they are awkward to retrofit once concepts exist. Ask with `AskUserQuestion` rather than in prose, in two steps: the first three questions in one call, then the publish question as a follow-up call only if the audience came back public or both (it does not apply to an internal-only wiki, and its relevant options depend on that answer, so it cannot share the first batch). Infer the title from the repo or project and confirm it. Skip ...