inkeep/open-knowledge

Codebase Wiki guides agents in generating and refreshing a source-grounded, version-controlled wiki of a codebase, with per-folder rules, freshness and log discipline, and audience/depth knobs. Use when the project has a wiki/ knowledge base or when asked to generate or refresh a wiki of the codebase.

Consolidate Notes promotes existing research into a stable-status canonical article under articles/. Use it when a decision has been made and the team wants the source of truth written down, or when asked to consolidate, canonicalize, promote research, or supersede an older article.

Frame a Proposal turns a problem into a reviewable RFC-shaped design document under proposals/. Use it when asked to frame a proposal, write an RFC, propose a design, pitch a change, or draft a PRD-style design doc.

Knowledge Base defines the three-layer source-grounded layout (external-sources, research, articles) and the per-folder rules and status flows for working in a Knowledge Base project. Use it when setting up or operating a project with ingest-research-consolidate stages.

Note Taking guides agents on how to work in a Plain Notes project, a flat notes folder plus a daily journal for jotting notes, capturing quick thoughts, and writing today's journal entry. Use it when the project has these folders or when asked to capture a thought or write a daily entry.

Open Knowledge defines the agent-runtime contract for working inside an OpenKnowledge project, a markdown-CRDT knowledge base exposed over MCP. Use it when reading, listing, searching, editing, or linting any .md or .mdx file, and before any mcp__open-knowledge__* tool call.

Open Knowledge Format provides guidance for creating, reading, reviewing, and maintaining OKF v0.2 bundles. Use it when responding to OpenKnowledge okf plugin warnings or when choosing types, provenance, links, indexes, or logs.

OpenKnowledge Discovery explains what OpenKnowledge is, how to install it on a repository with ok init, how to share a project, and how to open a single markdown file outside a project.

OpenKnowledge Skill Authoring guides the creation of Agent Skills (SKILL.md files) by checking existing skills, resolving scope, and structuring progressive-disclosure instructions. Use it when writing a new skill for OpenKnowledge or an editor.

Personal CRM structures people, companies, and meetings as typed dossiers with compiled truth and append-only timelines. Use it when capturing notes about a person or company, logging meetings, prepping for meetings, or answering who someone is and what was last said.

Record a Decision captures a settled architecture choice as a Nygard/MADR-shaped ADR under decisions/, with context, options weighed, decision, consequences, and supersedes links. Use when recording an architecture decision, writing an ADR, or superseding an old decision.

Research with Sources investigates a topic against preserved sources and writes a draft-status research article under research/ in a knowledge base. Use it when asked to research a topic, compare options, synthesize sources, gather evidence, or extend an existing research doc.

Review a Design evaluates whether a design is sound—solving the right problem and following from its stated goals and constraints—and returns ranked, evidence-backed findings, not edits. Use it to pressure-test proposals, specs, ADRs, or architecture decisions before committing to them.

Software Lifecycle defines how docs flow from proposals to decisions to specs to postmortems, plus guides, and carries per-folder rules and agent behaviors. Use it when the project has these folders or when asked how the project is organized.

Worldbuilding helps manage a fiction encyclopedia of characters, settings, themes, factions, and lore. Use it to auto-stub new entities, link related entries, and flag internal inconsistencies in the world.

Write a Postmortem produces a blameless incident postmortem following the Google SRE shape — evidence-based timeline, trigger vs root cause vs symptom, contributing factors, what went well, and owned+dated+verifiable action items. Use it when asked to write a postmortem, do an incident review, or document an outage.

Write a Spec scopes a feature end to end and writes an implementation spec under specs/ from an accepted proposal, including current-system mapping, goals/non-goals, a Decision Log, an Open Questions backlog, and a migration + test plan.

Writing Workflow manages a three-stage drafting flow (ideas → drafts → published) for essays, newsletters, and blog posts. Use it when working in a writing-pipeline project or when asked to capture an idea, start or revise a draft, review a piece, or publish it.