initiative:edit
initiative:edit
Section titled “initiative:edit”Edit initiative fields and phase metadata
Options:
| Flag | Description | Required |
|---|---|---|
-i, --id <initId> | Initiative ID | No |
--title <text> | Replace the initiative title field | No |
--status <status> | New status (draft, open, in_progress, done, archived) | No |
--priority <priority> | New priority (P0, P1, P2, P3) | No |
--blocked-by <initId> | Initiative ID that blocks this initiative | No |
--blocked-reason <text> | Reason for blocking (required with —blocked-by) | No |
--unblock | Remove blocked_by and blocked_reason fields | No |
--add-lane <lane> | Lane to add (repeatable) | No |
--remove-lane <lane> | Lane to remove (repeatable) | No |
--notes <text> | Note to append to notes array | No |
--description <text> | Replace the initiative description field | No |
--add-phase <title> | Append a new phase with auto-incremented id and pending status (repeatable) | No |
--add-success-metric <text> | Append to success_metrics array, avoiding duplicates (repeatable) | No |
--remove-success-metric <text> | Remove exact match from success_metrics array (repeatable) | No |
--phase-id <id> | Phase ID to update (use with —phase-status) | No |
--phase-status <status> | Update phase status (pending, in_progress, done, blocked) | No |
--phase-title <title> | Update phase title (use with —phase-id) | No |
--created <date> | Set created date (YYYY-MM-DD format) | No |
--phase-execution-order <order> | Phase execution order (sequential, parallel) | No |
--dependency-model <model> | Dependency model for the initiative | No |
--from-clean-snapshot | Run the edit in a LumenFlow-owned micro-worktree based on origin/main; never reads or writes the caller checkout. Allowlisted to —status / —phase-id / —phase-status / —notes / —add-success-metric / —remove-success-metric. Refuses if write set targets a dirty foreign WU yaml or escapes the allowlist. | No |
--from-clean-snapshot-dry-run | Emit the snapshot audit record without performing UnsafeAny git operations. Use to verify the safe-bypass justification before executing. | No |