Skip to content
Cockpit0.29.0
A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live

I0005

Implement the plan command surface

Where it stands

devtask.issue
Readiness
complete completion is recorded and every required evidence token is present
Status
DONE
Can start
not now
Milestone
Milestone status
DONE
Wave
4
Waiting on
none
Holds back
Behind it in all
8
Evidence
1 of 1
A move writes the repository: it stamps one field of this issue's record and appends one event to the ledger, and a commit will carry both.
The same moves from a terminal

majordomus plan start I0005

majordomus plan verify I0005

majordomus plan done I0005

What it is

Objective
Give a worker one command that answers what is ready, why something is blocked, what the graph looks like, and that moves an issue through its lifecycle while refusing illegal transitions.
Why
A model nobody can query is a filing cabinet. The command is how a fresh session with no conversation history finds its work.
Now
The engine existed with no interface.
Wanted
majordomus plan validate, status, list, show, ready, blocked, waves, graph, next, body, start, verify, evidence and done all read the one model.
Done when
unknown: the record declares no `completion`
Risk
Low

Acceptance

  • plan start refuses an issue that is not READY
  • plan done refuses while a required evidence token has no evidence
  • plan evidence refuses a token the issue does not require
  • plan evidence refuses without a command or an artifact
  • every subcommand answers --help and an unknown one exits 2
Validation
bash test/run.sh 43_plan_command
Evidence required
command_test
Evidence present
command_test

Scope

Touches
lib/plan.shbin/majordomusdocs/CLI.md
Not
Any network call; the CLI never leaves the machine
Depends on
Priority
p0
Profile
implementation
Parallel safe
false
Owner
unknown: the record declares no `owner`

The work so far

Branches
none
Merged
none
Commits
0
Trunk
master
Sessions
none
Created
2026-09-04
Updated
2026-09-04T03:12:53Z
Started
2026-09-04T03:12:50Z
Verified
2026-09-04T03:12:51Z
Completed
2026-09-04T03:12:53Z

Synchronisation

Adapter
scripts/github-sync
Repository
unknown: the derived plan's header carries no repository
External issue
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
State there
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it

Findings

Nothing is wrong with these records.