Run a task toward an explicit goal

Give a long task a finish line#

Use /goal to set a verifiable completion condition and keep a conversation working toward it.

Write a checkable condition#

Confirm project, model, and permissions. Name the result, evidence, and action boundaries. A goal defines completion; a schedule defines when work runs.

Onevium has displayed Goal progress since 1.1.19. Avoid unlimited objectives such as “make everything perfect.” A time or iteration instruction in a prompt is not a hard resource quota.

Set the first goal#

1. Send the example in the intended conversation.
2. Inspect the goal indicator and investigation records.
3. Check whether each pass adds evidence rather than repeating failures.

/goal Inspect this project's member-invitation flow.
Complete when the UI entry, server permissions, expiry behavior,
and relevant tests each have source-file references.
Mark missing evidence explicitly. Do not edit files or run services.
If a required repository is unavailable, report the blocker and stop.

Read progress and completion#

Progress shows the condition, iterations, elapsed time, and latest evaluation reason. Send /goal to inspect status.

Success means every completion criterion has actual evidence. Open the cited files and results even after completion is reported; evaluation cannot replace an unrun test.

Stop or correct a goal#

• Repeated failure: interrupt and inspect missing dependencies or ambiguous criteria.
• No longer needed: send /goal clear and confirm status before setting another goal.
• Waiting for approval: handle the actual request; Goal does not expand authorization.
• App interrupted: check current state rather than assuming automatic recovery.

Choose the next workflow#

See scheduled runs for time-based work, permissions for action boundaries, and projects and sessions for handoffs.