How to

Advance accepted-plan tasks

Inspect and advance the ordered execution ledger one task at a time.

What changes

task lists accepted-plan tasks and records start, block, unblock, implementation submission, and completion transitions. Only one task may be active, and completion derives from current verification and review facts.

When this helps

After an accepted plan initializes task-1 through task-N.
Before editing or submitting evidence for the current plan task.
After current spec, quality, verification, and finding gates make a submitted task eligible to complete.

Run this command

terminal

$sumr mission task list SUM-123# inspect ordered tasks$sumr mission task start SUM-123 task-1 --actor codex# start one task$sumr mission task submit SUM-123 task-1 --from task-1.md --actor codex# submit implementation evidence

Flags you can use

--actor <name>

Name the actor claiming or advancing the task.

--kind <kind>

Classify a blocker as context, technical, plan, or external.

--reason <text>

Record the task blocker reason.

--from <file>

Import the bounded implementation artifact for task submission.

--allow-custom-key

Accept a work key that does not match a configured work-provider prefix. Use only for local or intentionally custom work.

--json

Return a structured JSON envelope for scripts, CI jobs, and AI assistants.

--help, -h

Show the command syntax, supported flags, and examples without changing files.

Keep in mind

Accepted plans must use contiguous top-level ### Task N: Title headings starting at 1.
Submission records the current full Git SHA and artifact hash; it does not run verification or review.
A task completes only with current passing spec and quality reviews, a current passing task receipt, and no open critical or important findings.