The idea is not clear yet
Use plan mode for ideation, scope cuts, architecture, role division, and risk checks.
Plan before build
Plan when the work is fuzzy. Execute when the steps are clear.
Plan mode is for deciding what to do. Goal mode is for pushing one clear objective to completion. Execution mode is for carrying out a specific checklist.
Use Plan Mode When
The work affects the whole pod
If several people depend on the answer, plan first so the group does not split in different directions.
The model might edit files
Ask it to read and plan before it changes anything. Review the plan before execution.
You need to save tokens
Use the best model to make the plan, then switch to a lower/faster model for bounded execution.
Copy This
Planning prompt.
/plan We are building [project]. We have [time], [people], and [constraints]. Ask what is missing, then make a step-by-step plan we can divide across the pod. Keep the first version small enough to finish today.
Goal prompt.
/goal Complete the first working version of [project] without stopping until [verifiable end state]. Keep changes small, test after each checkpoint, and pause if setup, credentials, or product direction is unclear.
Claude Code version.
Start in plan mode. Read the folder first. Do not edit files yet. Give us the smallest version we can finish today, the roles each pod member should take, and the first three build steps.
Say slash commands, not backslash commands. The slash is the command prefix.