Your decisions, addressable
in every AI tool you use.

Draftlize cards are the substrate. CLI mirrors them into your repo as markdown. MCP server exposes them to Claude Code, Cursor, and Claude Desktop as first-class context. When you implement c-12, mark it built — when the spec moves, status auto-flips to drift_detected and you know what to revisit.

Get started Claude Code →

FIG. 1 · INTEGRATION SURFACES

Four ways your cards land in your tools.

A · CLIdraftlize pull

CLI — `draftlize pull` to your repo

Cards land at `.draftlize/cards/<id>.md` as plain markdown with YAML frontmatter. Claude Code reads them as ambient context. `draftlize flag c-7 "..."` writes a gap card back to the GapLedger for user review.

B · MCP SERVERstdio JSON-RPC

MCP server — stdio JSON-RPC

Independent `draftlize-mcp` binary speaks JSON-RPC over stdio. Tools: `read_card` / `list_cards` / `search_cards` / `propose_card` (locked to fact/statement/question). URI: `draftlize://<slug>/<cid>` resolvable via `/api/resolve`.

C · SLASH COMMANDS/draftlize:cite

Slash commands — `/draftlize:cite c-7`

After `draftlize link <project>`, four slash commands land in `.claude/skills/draftlize/`: `/draftlize:cite` / `/draftlize:flag` / `/draftlize:fact` / `/draftlize:status`. Claude Code resolves them inline.

D · STATUS TRACKINGmark-built

implementation_status — spec drift tracking

`draftlize mark-built c-12` flips the card's status to `built`. Edit the card later and status auto-flips to `drift_detected` — the agent knows what was implemented from which snapshot, and what's moved since.

Cards as code context. Specs that don't drift.

New accounts get $5 freeExport your data anytimeNo lock-in · export anytime

Start with $5 free, then pay only for what you use — no subscription, balance never expires. Full CLI + MCP + slash commands, all included.

Get started

Your decisions, addressablein every AI tool you use.