QUBE Command Surface: Idea to Complete Implementation

Use QUBE as the entrypoint and dispatcher. Bootstrap owns planning, Executor owns issue and PR execution, Quality owns evidence, and Umpire owns continuation policy. The surface keeps make-it-so prominent while staying readable and avoiding protected franchise UI patterns.

QUBE Bootstrap Executor Quality Umpire Current handoff gap

1. Discover

QUBE

qube make-it-so "..." qube components qube run <tool> -- --help

Confirms installed component versions and the available command family.

2. Capture Idea

Bootstrap

qube aib init . --agent codex --idea "..." --json qube aib next --json qube aib answer --field <field> --value <answer> --json

Turns the fuzzy request into structured planning state.

3. Accept Spec

Bootstrap

qube aib spec draft --json qube aib spec validate --json qube aib spec accept --section <id|all> --json

Implementation should not start until the right sections are accepted.

4. Work Items

Bootstrap

qube aib milestones generate --json qube aib work-items generate --json qube aib work-items render --provider github --dry-run --json

Produces provider-ready work item drafts.

5. Issue Handoff

Boundary

review rendered GitHub issue draft create or confirm real GitHub issue

Current gap: Bootstrap renders issue output; Executor starts from real provider issues.

6. Execute Issue

Executor

qube aie queue --json qube aie start next qube aie view <issue> qube aie branch check <issue>

Selects one valid issue and moves work onto the issue branch.

7. Implement + Audit

Executor

edit code, tests, and docs qube aie audit ui <issue> --prepare qube aie run start --name ui-audit -- <dev command> qube aie run wait --name ui-audit --url <url> --timeout 30 qube aie run stop --name ui-audit

Uses managed local app runners for UI evidence when needed.

8. Quality Evidence

Quality

qube aiq setup --format json qube aiq doctor --format json qube aiq plan . --format json qube aiq run . --format json qube aiq evidence --format json

Produces trusted machine-readable gate evidence.

9. PR To Completion

Executor + Git

qube aie pr body <issue> git commit && git push open non-draft PR that closes issue qube aie pr view <pr> --json qube aie pr gate <pr> --json merge after approval, CI, and gates qube aie complete <issue>

PR helpers do not silently merge. Merge happens only after policy passes.

Failure Loop

If Quality, CI, review, or UI audit fails, return to implementation, fix the concrete issue, rerun the affected gate, then rerun qube aie pr gate <pr> --json.

Continuation Loop

After merge and qube aie complete, Umpire can inspect trusted state with qube aiu status --json, host hooks, or whip tasks before the next issue starts.