Codex Goal Builder

Core Rule

create_goal

get_goal

Workflow

1. Capture the user's rough objective in one sentence.
2. Decide whether a Goal is appropriate.
   • Use a Goal for multi-step work with a durable objective, uncertain path, and evidence-based completion.
   • Prefer a normal prompt for one-line edits, simple explanations, short reviews, or tasks with no durable finish line.
3. Draft a stronger Goal using this contract:

<desired end state>, verified by <specific evidence>, while preserving <constraints>. Use <allowed inputs/tools/boundaries>. Between iterations, <how to choose and record the next action>. If blocked, budget-limited, or no defensible path remains, stop with <evidence gathered, attempted paths, blocker, and next input needed>.

1. Ask only the missing high-leverage questions.
   • Ask 1-3 questions at a time.
   • Infer safe defaults when the answer is obvious from repo context or the user's wording.
   • Prefer questions about evidence, constraints, and boundaries over vague preference questions.
2. Produce a final Goal in one of these forms:
   • CLI text:

     /goal ...

   • Active tool call:

     create_goal(objective=...)

     , only after explicit approval.
3. If the user provides a token budget, pass it to

   create_goal

   . Otherwise omit it.

Goal Checklist

• Outcome: what must be true when done.
• Verification surface: tests, benchmarks, logs, screenshots, artifacts, reports, or source evidence.
• Constraints: behavior, API, data, security, design, performance, or compatibility that must not regress.
• Boundaries: allowed repositories, files, commands, environments, services, or data sources.
• Iteration policy: how Codex should choose the next attempt after each result.
• Blocked stop condition: what counts as honestly blocked and what to report.

Question Strategy

• Missing verification: "What command, artifact, metric, or evidence should prove this is done?"
• Missing constraints: "What must not change while Codex works on this?"
• Missing boundaries: "Which repo/files/environment may Codex touch or inspect?"
• Missing blocked condition: "If this cannot be completed, what should the final report include?"

Output Style

/goal

text

• "当前草案"
• "还差的问题"
• "确认后可启动"

create_goal

Safety

• Remember that Codex Goals are thread-scoped persistent objectives, not global memory or project instructions.
• Never represent a budget limit as success.
• Never mark a Goal complete unless concrete evidence satisfies the objective.
• Do not use

  update_goal

  to rewrite, pause, resume, or clear Goals; those lifecycle controls belong to the user or system.
• For live systems, database writes, production deployment, payments, account changes, or destructive operations, include explicit boundaries and require explicit user approval before action.

References

references/goal-patterns.md