@cubedot/cli

Connect a repo to your Cubedot project and drive a spec-first build loop with your AI coding agent. The CLI wires up the Cubedot MCP server, generates the project constitution and agent specs, and owns the local progress ledger.

Install & connect

Copy the command from your project's Integrations page in the Cubedot web app. It looks like:

npm i -g @cubedot/cli && cubedot init --token <TOKEN>

Run it in your project folder's terminal, then open Claude Code in that same folder and reload.

init validates the connection, writes .mcp.json and the agent assets (CLAUDE.md / AGENTS.md, the Feature Implementation Agent + Verifier), and creates the .cubedot/ ledger.

Commands

| Command | What it does | |---|---| | cubedot init | Connect + scaffold the repo (--token, or --project/--key/--url) | | cubedot sync | Refresh the local projection and detect drift | | cubedot status | Connectivity + file-health check (read-only) | | cubedot check | Validate markers/config (read-only, CI-friendly) | | cubedot work | List all unblocked functionalities — dependency-aware, not a strict sequence (aliases: next, todo) | | cubedot start <FN> | Set a functionality to in_progress | | cubedot complete <FN> | Set a functionality to code-complete | | cubedot done <FN> | Mark a functionality done (human gate; --discrepancy to record open criteria) | | cubedot progress | Print the completion summary (read-only) |

Requires Node.js ≥ 18.

Support

Issues and questions: https://cubedot.ai