docs-cockpit

Radar Flight Deck for repo-native docs

docs-cockpit

A skill-first project cockpit for AI coding agents.

Codex and Claude Code can write fast. docs-cockpit gives that output a durable schema, validates markdown frontmatter, and renders a local single-file dashboard your repo can keep.

MIT licensed Python renderer Local file:// output Version 1.3.1

Product proof

Operational Kanban from markdown your agents already write.

The dashboard is a rendered view over repo files: cards, validation status, linked markdown previews, and machine-readable state for follow-up workflows.

docs-cockpit dashboard showing kanban cards, validation status, and linked markdown preview

Codex

codex plugin marketplace add Guohao1020/docs-cockpit
codex plugin add docs-cockpit@docs-cockpit

Claude Code

/plugin marketplace add Guohao1020/docs-cockpit
/plugin install docs-cockpit@docs-cockpit

Workflow

Skills reason. Python renders. Your markdown stays the source of truth.

The v1 workflow moves cognition into agent skills and keeps the CLI deterministic, which makes the dashboard explainable, repeatable, and easy to verify in git.

1

SessionStart router

When a repo has docs-cockpit.yaml, the plugin injects the entry skill and routes setup, rebuild, render, and upgrade requests.

2

docs-cockpit-build

The first-build skill discovers modules, reasons about doc associations, asks when anchors are uncertain, and writes the cockpit config.

3

docs-cockpit-rebuild

The refresh skill reads existing state.json, diagnoses drift, re-infers minimal changes, and preserves stable associations.

4

docs-cockpit render

The CLI validates frontmatter, embeds linked docs, emits state.json, and writes a single HTML dashboard for local use.

Feature set

Built for AI coding power users who still want deterministic artifacts.

docs-cockpit is not another hosted tracker. It is a plugin-guided markdown workflow with a renderer you can run, diff, and audit.

schema

Frontmatter validation

Every document is checked against the canonical schema and reports structured error, warning, and hint issues with references.

state.json

Machine-readable sidecar

Rebuild workflows and external checks can read stable dashboard state without scraping rendered HTML.

file://

Local dashboard output

The rendered dashboard is a static file you can open locally, publish with GitHub Pages, or commit as a project artifact.

plugins

Codex and Claude Code

Both plugin workflows are supported now, sharing the same skills, hooks, commands, schema, and release version.

upgrade

docs-cockpit upgrade

The upgrade command handles CLI and plugin-layer updates, release notes, cache clearing, and restart guidance when skills change.

renderer

Deterministic Python CLI

The CLI renders and validates. Association reasoning lives in skills, keeping output mechanical and easier to trust.

Audience

For builders letting agents produce serious project memory.

If your plans, specs, RFCs, and implementation notes live in markdown, docs-cockpit gives agents a shared operating surface without moving data out of the repo.

AI coding power users

Keep Codex and Claude Code productive across multiple projects while making every generated doc conform to one schema.

Indie developers

Replace scattered agent notes with a project cockpit you can open locally, share as HTML, and keep under version control.

Toolsmiths and teams

Use state.json and validation output for CI checks, health reports, and agent handoffs without adopting a SaaS tracker.

FAQ

Current support, local data, and agent adapters.

Is Codex supported?

Yes. docs-cockpit ships a Codex plugin workflow with marketplace install commands, SessionStart routing, and skills shared with the Claude Code surface.

Is Claude Code supported?

Yes. Claude Code remains a supported plugin workflow and uses the same build, rebuild, render, and upgrade model.

What about other agents?

The core renderer and schema are agent-agnostic. Other agents can use the CLI today, while native adapter packaging can evolve around the same files.

Does the dashboard need a server?

No. docs-cockpit render writes static HTML and state.json. You can open the dashboard from file:// or host it as static assets.

Why use skills instead of a smarter CLI?

Agents are better at judgment and dialogue. The CLI is deliberately mechanical, so rendering and validation stay deterministic.

How do upgrades work?

Run docs-cockpit upgrade. It checks CLI and plugin versions, shows release notes, clears plugin cache when needed, and explains the restart step.

Start

Give your AI-written markdown a cockpit.

Install the plugin, open a repo, and let the skills build or refresh a schema-validated dashboard over the markdown already on disk.