How to

Register a plan

Attach the implementation plan for review and approval.

What changes

plan records a draft plan artifact used for approval and implementation. It can write a template or read existing Markdown from a file; only a separately accepted plan satisfies the approval gate.

When this helps

The work has been researched and needs a reviewable plan.
A planner produced plan.md and the workflow needs to record it.
A human needs a stable draft to review before approval is recorded separately.

Run this command

terminal

$sumr mission plan SUM-123 --from plan.md# attach draft

Flags you can use

--from <file>

Read the plan body from an existing Markdown file.

--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

A generated template stays in draft status and does not satisfy a flow gate. Replace placeholders before approval.
Plan creation and approval are intentionally separate. Run sumr mission approve <issue-key> only after human review.
Do not approve a plan unless a human has actually approved it.
Keep implementation scoped to the approved plan.