Cod Doc banner
Orange-hanter Orange-hanter

Cod Doc

Documentation community

Description

Context Orchestrator for Documentation — MCP server + autonomous agent that keeps project docs honest. Docs, tasks, plans, stories, links, revisions in SQLite; markdown is a hash-verified projection, not the source of truth.

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

COD-DOC — Context Orchestrator for Documentation

PyPI Python 3.13+ CI License: MIT

Docs that drift from code are worse than no docs.
COD-DOC makes drift detectable — and gives both humans and LLM agents one shared, auditable interface to fix it.


Docs, tasks, plans, stories, links and revisions live in a database (`/.cod-doc/state.db`). Markdown is a *projection* of that state, not the source of truth — so a doc can never silently drift away from the task that changed it.

Features

  • Hash-verified docs. Every markdown file carries a content hash of the DB state it was projected from. cod-doc doc drift tells you exactly which file was edited behind the system's back.
  • Every edit is a revision. Full append-only history per document and per task, with revert — not a git blame on a 900-line file.
  • First-class links. Documents, sections, tasks, ADRs and git commits reference each other as rows. Renames cascade instead of rotting.
  • Task engine with atomic checkout. 7-state task lifecycle, dependency graph, plan sections, ready-queue — agents lock work instead of racing it.
  • Built for LLM agents. A dedicated 6-tool MCP profile (agent_pick, agent_report, agent_complete, …) gives an agent everything it needs in on