launch

name	launch
description	Initialize a persistent OmA workflow lifecycle and start staged execution.

Launch OmA workflow lifecycle.

Task: $ARGUMENTS

Launch protocol:

1. Initialize lifecycle metadata (mode, objective, acceptance criteria, owner assumptions).
2. Before mutating shared workflow state, read .omg/state/session-lock.json.
   • if no lock exists, create/update it for the current orchestration session
   • if another active session owns the lock, do not overwrite shared workflow artifacts; write only session-local drafts under .omg/state/sessions/[session-slug]/ and report the conflict
3. If filesystem tools are available, create/update:
   • .omg/state/workflow.md
   • .omg/state/checkpoint.md
   • .omg/state/taskboard.md (only when a task graph already exists)
   • .omg/state/workspace.json (only when user provided path/lane scope)
   • .omg/state/hud.json (create default visibility=normal only if missing)
4. Run team-plan then team-prd.
5. For non-trivial implementation work, treat /oma:workspace set ... or existing workspace state plus /oma:workspace audit as the default preflight before execution.
6. Recommend /oma:taskboard sync after audit whenever the task spans multiple roots, parallel lanes, or any resume/handoff boundary.
7. Start first execution slice (team-exec) only when scope is clear and the active lane is clean/trusted enough for execution or review, with no unresolved baseline drift.
8. Report current stage, any preflight blocker, lock ownership status, and resume command.

Output format:

Lifecycle

• status: launched
• active mode:
• current stage:

Initialized State

• ...

First Execution Slice

• ...

Resume

• next command: