Write a good goal

Help the user turn a rough intention into one or more /goal objectives that goal mode can pursue across many turns without supervision. A goal is not a task description; it is a completion contract. It says what must become true, how that truth is proven, where the work may and may not reach, and when to stop and report.

Drafting and starting are separate steps. Settle the wording first. Only once the user has approved the exact objective should you call create_goal. When the user approves more than one objective, call create_goal for each approved goal in the intended order; the first starts and the rest are queued.

Ask, do not narrate choices

When a decision has concrete options, use the host's user-question tool if it is available. Do not write a prose menu and ask the user to answer in free text.

Examples of choices that should use the tool: