bloom-skip

$bloom --skip

Waive the CocoBloom commitment dialogue for the current project. This command is intentionally separate from $bloom so command loaders can route the flag path directly.

Preconditions

• .cocoplus/ must be initialized.

Behavior

1. Verify .cocoplus/ exists. If absent, output: "CocoPlus not initialized. Run $pod init first." Then stop.
2. Read .cocoplus/lifecycle/meta.json if it exists. If missing, create a new metadata object.
3. Set "bloom_waived": true.
4. Preserve all existing metadata fields, including current_phase, phases_completed, flow_type, and phase_history.
5. Write the updated JSON atomically.
6. Output:

Bloom waived. Run $spec — no advisory message will appear.

Downstream Effect

When $spec sees "bloom_waived": true, it does not display the CocoBloom advisory and does not attempt to load lifecycle/bloom.md.

Exit Criteria

• .cocoplus/lifecycle/meta.json exists.
• bloom_waived is exactly true.
• No bloom document is created.

Anti-Rationalization

Shortcut / Temptation	Why It Fails
Treat the skill as complete because the file exists	Skill contracts must describe observable behavior and verification, not just command names.
Skip artifact and safety checks for a small command	Small commands still mutate state or guide execution; preserve the same gates.