Goal

This skill creates the /goal instruction before execution starts. It does not perform the requested work unless the user explicitly asks to continue after the goal is written.

Operating Rules

• Keep the command prefix exactly /goal, even for Chinese users. The body may be Chinese.
• Put the best copy-ready goal first. Do not start with placeholders or a worksheet.
• Choose conservative defaults for low-risk ambiguity and state the assumption briefly.
• Ask only when the answer changes risk, cost, ownership, product direction, or permission.
• For specialized or unfamiliar domains, make the goal discovery-first instead of inventing domain rules.
• Treat verification, write boundaries, stop conditions, and pause conditions as required parts of the contract.
• Prefer commands, logs, screenshots, files, URLs, builds, tests, or other evidence over vague confidence.

Goal Contract

Every finished goal should contain these elements: