Plan

Use this skill to stop execution-first behavior on meaningful work.

Default pattern: clarify → plan → approve → execute → close.

Treat /plan as a read-only planning stance until approval. Safe reads are allowed: reading files, listing files, searching, inspecting docs, checking status, and other non-destructive exploration. Do not edit files, delete data, push commits, deploy, or run destructive or irreversible commands until the user approves a plan or explicitly says to skip planning.

Prefer the core lenses first. Use parallel and living only when the work is clearly big enough to justify the extra structure.

When to stay out of the way

Do not force planning for:

• trivial single-file edits
• simple factual questions
• obvious follow-up micro-actions
• work where the user explicitly says to skip planning

Command model