Guides & design specs
Everything you need to understand the data model, architecture decisions, and current feature state.
Reviews & Comments
Responsibilities, plan and spec reviews pinned to a version, Open/Guided/Gated workflows, and anchored discussion.
My Work
The inbox built from your responsibilities: bands, lenses, evidence gaps and the bell.
Email & Slack Notifications
Connect Resend and a Slack webhook, choose events per channel, personal opt-outs, mutes and retries.
Step-by-step deploy guides
Click-by-click setup on Railway, Fly.io, Render or Docker, from fork to first sign-in.
Deploying
Railway, Fly.io or Docker: choosing SQLite or Postgres, first sign-in at /setup, upgrades and settings.
Enterprise Extensions
The narrow hooks the community edition exposes, and what they are for.
Collaboration, Review & Notifications Spec
The design behind responsibilities, reviews, comments, My Work and notifications.
App Spec
Complete spec of the current app: schemas, views, query/mutation API, access rules, and wiring gaps.
How CodePlans Thinks
The conceptual map: what products, assets, plans, and releases are each for, the boundary rule between them, and the five design principles behind the tool.
Agent Skills
Install the CodePlans skills in Claude Code (a plugin that also connects the MCP server) or any agent with npx skills add, and what each skill does.
Capturing a Docs Corpus
The /codeplans-capture skill: turn an existing /docs folder into plans, tasks, and tech-debt items, each linked to a native versioned spec, with its original Markdown URL retained as provenance.
Logging Work via Claude
The /codeplans-log skill: turn "document what we just did" into plans, tasks, PR records, and work items at the end of any session.
Modeling Monorepos
Break a large codebase into assets without over-modeling: the asset test, tiered libraries, curated dependency edges — and a Claude skill that does it for you.
Product Wiki
Read your product as a connected library: asset pages, full document readers, searchable content, delivery context, and creator/editor provenance.
Native, Versioned Specs
Author and link specs, track delivered versions, revise with design notes, and migrate legacy git URLs safely on SQLite or PostgreSQL.
Releases & Versions
Group plans that ship together, stamp per-asset versions, derive release notes from delivered work, and ship with a trustworthy record.
Asset History & Design Log
The version-structured timeline every asset builds for itself, and how humans and agents record design notes worth keeping.
The Asset Atlas
The live system map: lenses for health, debt, and activity, blast-radius hover, and the grid and table views beside it.
Command-line tool
Install @codeplans/cli, work with plans, tasks and work items from the terminal, and set up workspaces from a manifest with codeplans apply.
Working with AI Agents
Connect Claude Code, Cursor, and friends over MCP: the full 75-tool catalog, recommended agent workflows, and the AI drafting flags.
Native Spec Entity v1
The data model and decisions behind versioned specs, asset associations, immutable delivery receipts, and legacy URL imports.
Releases & Asset History Spec
The design behind v0.4.x: releases as delivery groupings, derived history, the design log, and feature-flagged AI drafting. All four phases shipped.
Asset Record Spec
The capabilities register per asset shipped in v0.4.4. Planned: agent-driven reconciliation against code and round-trip release publishing.
Asset Atlas Spec
The map shipped in v0.4.5, and its path from picture to planning surface: lens thresholds, transitive blast radius, and plans started from the map.
Layers & Boundaries Spec
Shipped in v0.4.6: the product-vs-asset rule made operational — asset layers, layer columns on the Atlas, and move_asset for refining a model.
MCP Server Spec
How the MCP endpoint works: Streamable HTTP inside the app, API-key auth with read/write scopes, and the design of the tools.
Design Spec v3
The canonical target design: work items, provenance-based integrations, per-asset PR tracking, and the phased roadmap (all phases shipped).
Historical Specs
Superseded v2-era functional spec and data-model plan, kept for the reasoning trail behind the current design.
Database Schemas
Current database schema diagrams covering both SQLite and Postgres configurations.
Current feature status
Transparent about what's wired, what's in progress, and what's coming.