CLI command reference
The @cubedot/cli drives the spec-first build loop from your repo. Requires Node.js ≥ 18.
| 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) |
Working
Section titled “Working”| Command | What it does |
|---|---|
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) |
The status lifecycle
Section titled “The status lifecycle”A functionality moves todo → in_progress → code-complete → done. done is a human gate, it’s the point where you confirm the work actually meets its acceptance criteria, not just that code was written. Record any open criteria with --discrepancy.
Troubleshooting
Section titled “Troubleshooting”See CLI troubleshooting for the common “Connecting…” and “command not found” fixes.