core-operate-documentation

name	core-operate-documentation
description	Use when creating, organizing, or updating project documentation and knowledge bases in any project — structure knowledge as an OKF bundle (markdown + frontmatter, index.md, log.md, cross-links) so both humans and agents can read, traverse, and maintain it.

Documentation & Knowledge

How project knowledge is recorded so that humans and agents can both read, traverse, and maintain it. The backbone is the Open Knowledge Format (OKF v0.1) — markdown files with YAML frontmatter, self-describing, diffable, portable. Applies to every track: this is a core skill inherited by all projects.

Source spec: OKF SPEC.md

Areas under consideration

• [] Where docs live — in-repo knowledge bundle, single source of truth
• [] Docs-as-code — diffable markdown, updated with the change, logged
• [] Agent-facing docs — the whole format is agent-consumable by design
• The required set — README, ADRs, runbooks, API docs: what every project must have
• ADR format & when a decision earns one
• CLAUDE.md upkeep specifics — what agents need recorded per project

Skill

When documenting a project, structure its knowledge as an OKF bundle

A knowledge bundle is a directory tree of markdown files, usually a docs/ or knowledge/ subdirectory of the repo (a git repo is the preferred distribution — history, attribution, diffs). Organize subdirectories by whatever grouping fits the domain; the structure itself carries no required meaning.

Every concept document gets frontmatter

One markdown file = one concept (a table, an API, a metric, a playbook, a decision — tangible or abstract). Frontmatter rules: