Bootstrap
Planning state, specs, milestones, and work item drafts.
Command deck for agent-assisted work
QUBE moves ideas to completed implementation.
Use one composer CLI to plan work, execute issue branches, gather quality evidence, inspect continuation state, and keep each component package independently installable.
QUBE
qube componentsBootstrap
qube idea "Ship a local notes CLI"Executor
qube start next --jsonQuality
qube check src --jsonUmpire
qube continue --jsonOne deck, five responsibilities.
QUBE keeps agent work explicit. The composer command routes to the installed package that owns each stage, so automation can use QUBE while single-package installs still work when a team only needs one tool.
- Compose
- QUBE discovers installed components and dispatches regular commands from one entry point.
- Plan
- Bootstrap turns intent into accepted specs, milestones, and provider-ready work item drafts.
- Execute
- Executor owns issue selection, branch policy, pull requests, review gates, and completion.
- Check
- Quality produces staged evidence for source, tests, packaging, and release readiness.
- Continue
- Umpire reads trusted state and tells an idle agent when continuing is safe and bounded.
The regular path stays readable.
QUBE uses product-language commands for the common workflow and keeps the advanced escape hatch available when a component command needs to be forwarded exactly.
qube make-it-so "Ship a local notes CLI" --dry-run --json
qube aib spec draft --json
qube aie pr gate 87 --json
qube aiq doctor --format json
qube run aie -- queue --json
Executor
Issue work, branches, pull requests, reviews, and completion.
Quality
Quality gates, evidence, package readiness, and reports.
Umpire
Trusted state inspection and bounded continuation prompts.
Visual profile for public surfaces.
The command-deck profile uses operational hierarchy, status lanes, precise grids, and the cardinal make-it-so command language while avoiding protected franchise marks and layouts.
Install the deck or only the station you need.
Use exact package versions and keep lifecycle scripts disabled where possible. The plain qube examples on this page require a global installation. For a project installation, use pnpm exec qube.
Project-local QUBE
Recommended for agents, hooks, CI, and repository instructions.
pnpm add -D --save-exact --ignore-scripts @tjalve/qube@0.2.12
Guided plan
Choose an agent harness, issue tracker, automated checks (CI), review mode, and package manager without installing hidden dependencies.
pnpm exec qube init
Single package
Install a component directly when you only need that package. Repository state still uses QUBE-owned paths.
pnpm add -D --save-exact --ignore-scripts @tjalve/aie@0.2.9