Skip to documentation
Updated Read as Markdown

Goals

On this page

AI agents: read the complete documentation index. Append .md to any docs URL for its Markdown version.

A goal describes the outcome you want Chief to work toward. It gives direction across multiple milestones. A milestone is one executable piece of that work, with a definition of done.

Before you start

Open a project with its relay connected and a ready planning agent. Follow the quickstart if you have not created a project yet.

Tell Chief what success looks like

Write the outcome, audience, constraints and priority in project chat. For example:

Goal: make it easy for a new tester to set up this project.
Success means they can follow the README from a clean checkout.
Use the current stack, keep the scope to documentation, and ask me
before changing any deployment or account settings.
Propose the smallest useful milestone first.

Chief uses your goals and project context to propose work and may ask questions first. Answer those in chat. Review proposed goals before approving them; stating a goal does not itself approve every milestone toward it.

Expected result: the agreed outcome appears under Goals, and related work appears as proposals in Tasks.

Maintain your goals

Use Add goal in Goals to add an outcome directly. Expand a goal to see its available actions, including editing its wording or marking it done. You can also discuss priorities and changes with Chief in chat. Check the resulting goal list after a change so the current outcomes match your intent.

Keep goals about outcomes. Put a specific deliverable and its checks in a milestone. If priorities change, tell Chief what now matters most and review existing proposals before approving more work. A goal marked done records an achieved outcome; inspect the milestone results before making that decision.

From goal to completed work

  1. Agree on the goal and answer Chief's questions.
  2. Read the proposed milestones, including scope and definitions of done.
  3. Approve an appropriate small task with Go, or request a change with Revise.
  4. Check manager tasks when progress depends on your decision or review.
  5. Read completed results in History, use Activity for events and Summaries to catch up, and update your goals as outcomes are achieved.

When no useful milestone appears

Give Chief a narrower outcome, a concrete constraint, or the missing context in chat. Check that the Chief provider is ready; agent setup and troubleshooting explain readiness and usage failures. Once the manual loop works, consider auto mode.