CLIMission
How to
Initialize delivery state
Set work and repository providers, flow, and accepted keys.
What changes
init prepares a repo or workspace to track AI-assisted delivery work with a consistent flow, provider mapping, and issue-key policy.
When this helps
- A repo has not used the delivery workflow before.
- The work provider, repository provider, accepted issue prefixes, or delivery flow needs to be set.
- A team wants repeatable delivery state before people or AI assistants start work.
Run this command
sumr mission init# interactive setupsumr mission init --tracker <work-provider> --git-provider <repository-provider> --flow standard-delivery# configured provider rolessumr mission init --tracker <work-provider> --prefix SMR --prefix OPS --flow planning-only# multiple prefixesFlags you can use
--tracker <type>Set a registered work provider. Read current ids with mission providers.
--provider <type>Alias for --tracker.
--git-provider <type>Set a registered repository provider. Read current ids and capabilities with mission providers.
--flow <preset>Choose basic, planning-only, standard-delivery, or full-delivery gates.
--prefix <value>Add an accepted issue-key prefix. Repeat the flag for multiple prefixes, such as SMR and OPS.
--yesUse defaults and skip interactive prefix setup.
--jsonReturn a structured JSON envelope for scripts, CI jobs, and AI assistants.
--help, -hShow the command syntax, supported flags, and examples without changing files.
Keep in mind
- The delivery flow controls when work pauses for plan approval, implementation, validation, and handoff.
- Run
mission providers --jsonbefore sync. Use native sync only when the configured work provider reportsissueContext: true; otherwise record substantive context withmission sync <key> --from <file>. - Use remote PR creation only when the configured repository provider reports
pullRequestCreation: true; otherwise keep PR work in preview or manual handoff. - Use accepted prefixes to keep work keys specific and consistent.