Objective Crafter

Create a concise, auditable /goal command. Do not implement the task. Do not start a Goal unless the user explicitly asks you to create it in the current thread.

Fit Check

First decide whether a Goal is appropriate.

Use a Goal when the task has:

• a durable objective that may need multiple turns,
• an evidence-based finish line,
• an uncertain path where the next step depends on what Codex learns.

Good fits: performance tuning, flaky test investigation, bug hunts requiring reproduction, dependency migrations, multi-step refactors, benchmark-driven optimization, PR queue cleanup, release readiness audits, research reproduction, evidence-backed product or technical audits.

Poor fits: one-line edits, simple explanations, short code reviews, single command questions, vague wishes like "make this better", or tasks where the user wants one answer and then a stop.

If the task is a poor fit, say so briefly and provide the better normal prompt instead of forcing a Goal.