The Goal template makes your AI turn an objective into a measurable target with a timeline, hold it active while initiatives and tasks are linked under it, then review progress against the metric. You approve the target before tracking starts and approve the close. Reject the review and it returns to active.
4 steps · 2 approvals · 1 loop back · waits for child tasks
example · the steps are this template's real steps
For founders and team leads who set quarterly objectives and want progress tied to the actual work, not to a status meeting.
It is a stored workflow, not a prompt. Your AI client receives one step at a time from ConvOps over MCP, does the work, and advances. The engine holds the run at each of its two approvals until a person says yes.
4 steps, in this order. Below each one is the instruction your AI receives at that step, exactly as the template stores it.
Define the goal with a measurable outcome and timeline.
Confirm:
Record the answers in the goal's description or metadata. Request operator approval before activating.
no rejection path · the run moves on only when approved
Goal is now active. Create or link child work items that drive toward this goal: initiatives for committed bodies of work, or direct tasks/bugs for standalone items. Types are semantic; pick what matches the work.
This step is the steady state: the goal stays here while work is in progress. Advance to review when ready for a progress check or when the timeline milestone arrives.
Review progress toward the goal's measurable outcome.
Report:
If the goal is met, request operator approval to close it. If still in progress, reject to return to the active state and continue working.
rejected → back to Active
Goal achieved. Record the final outcome and close it out.
Two steps wait for a person. You answer in the chat; the engine records the verdict and the audit row records who gave it.
A goal without a measurable outcome and a timeline cannot be reviewed. You approve the target and how success is measured before the goal goes active.
what you review
no rejection path · approve to continue
Your AI reports the status of linked child work, progress on the metric and whether the timeline still holds. Approve to close, or reject to return to Active and keep going.
what you review
reject → back to Active
gates the engine checks without you
Read from the template's own steps: the tools they call, the files they write, and whether they touch code.
Connect your AI client first, then install Goal from the catalog in the ConvOps app. See how to connect a client
An installed template is a workflow in your workspace. Ask your AI to change it in plain words; the edit lands on the one step that needs it.
new chat
more example prompts
Yes. The Active step waits for child work to finish but allows an empty goal, so you can activate the target first and link initiatives or tasks as they come.
Active is the steady state. Your AI advances to Review when you ask for a progress check or when the timeline milestone arrives. Rejecting the review returns the goal to Active.
Initiatives for committed bodies of work (the Feature template attaches to initiatives) or direct tasks and bugs for standalone items. The catalog lists Feature as this template's dependency.
Any MCP client connected to ConvOps. Verified clients: Claude Code, Claude (desktop, web, Cowork), OpenAI Codex, ChatGPT, Cursor, OpenCode. It needs no repository, so a plain chat client works.