Choose a goal or rubric
Use a goal when you have one measurable objective and want Deep Agents Code to draft acceptance criteria before it starts. A goal has a lifecycle: it stays active until the agent marks it completed, blocked, or you clear it. Use a rubric when you already know the criteria you want the agent graded against. A rubric can apply to the next turn only or persist across future turns. Common patterns:- One objective, agent drafts criteria: Use
/goal <objective>. - Persistent criteria for every turn: Use
/rubric set <criteria>. - Criteria stored in a file: Use
/rubric file <path>. - One-turn quality gate: Use
/rubric next <criteria>.
Use a goal
Use/goal when you know the outcome you want, but want Deep Agents Code to propose the acceptance criteria before work begins. Goals are useful for open-ended work: the agent turns an objective into a concrete definition of done, then iterates until those criteria are satisfied.
/goal show to inspect the current goal. Use /goal clear to remove it.
Use a rubric
Use/rubric when you already know the acceptance criteria and want them to act as a quality gate for the agent’s work.
Rubric command reference
Rubric command reference
/rubric show: Inspect the active rubric./rubric clear: Remove the active rubric./rubric model <provider:model>: Set the model that grades rubric results.
Use rubrics in non-interactive mode
Use rubrics in non-interactive mode
Non-interactive runs cannot pause for goal review. Use You can also set the grader model and maximum grading iterations:
--rubric for tasks where criteria are already known:See also
Connect these docs to Claude, VSCode, and more via MCP for real-time answers.

