Goals

A goal is an outcome you want built, such as "Task priority support" or a new landing website. You name it and describe it the way you would to a colleague. Kadmo writes the epic, an agent analyses it, you settle the open decisions, an agent plans the work as tasks, and the tasks run on your agents wave by wave. The Goals page shows every goal, where it stands and whether it is waiting for you.

Experimental

Goals is an experimental feature in this release. It is off by default. To turn it on, open Settings → General and switch on Experimental features. The switch applies to everyone in the account. While it is off, Goals is hidden from the navigation and its pages are closed.

How a goal runs

A goal goes through a fixed path of steps. Each step either runs on its own or waits for you, depending on its settings.

Step	What happens	Where it can wait for you
Create	Kadmo creates the goal and writes its epic in your tracker project, with your description as the brief. Then it queues the analysis.	Before the analysis, you can choose or suggest the epics the goal covers.
Decide	An agent analyses the epic and returns a list of decisions and open questions, each with a recommendation and a confidence score.	Any decision below your confidence bar asks you.
Plan	An agent walks the current state of the product, writes a plan and breaks it down into tasks in the epic, with blocked-by links, grouped in waves.	Can be held before it starts.
Build	Each task runs on its own delivery playbook, wave by wave, through the task pool.	Steps only a person can do show as Your turn.
Results	The record of the goal: tasks, code, tokens, tracker and artifacts. Always open, not a step that runs.	Never

Between Decide and Plan, and between Plan and Build, a 10-minute window runs when nothing needs you. When it ends, the next step starts by itself. During the window you can press Hold to stop it, or start the next step at once (Start the plan now, Dispatch all N tasks).

Goal types

A goal's type, which the app calls its recipe, decides its steps.

Recipe	Steps	Holds by default
App feature (the default)	Decide → Plan → Build → Results	None
Landing website	Scope → Decide → Plan → Design → Build → Launch → Results	Design
Documentation site	Scope → Decide → Plan → Build → Launch → Results	Decide and Launch

The two website recipes start with a Scope step and ask a fixed set of alignment questions before work starts:

• Landing website asks about the conversion goal, audience and offer, brand identity, content and media, domain and hosting, legal and compliance, and analytics and tracking. Its Design step waits for Approve the mock, and its Launch step waits for Approve the launch.
• Documentation site asks about the source allowlist, the staleness ledger, a confidence floor, the sitemap draft and the deploy target.

Compare recipes › on the New goal page opens a side-by-side view of every recipe. A recipe marked Planned is shown there but cannot be started yet.

Create a goal

1. Open Goals and click + New goal.
2. Enter the Name, for example Task priority support. The goal's link is made from it, so it needs at least one Latin letter or digit.
3. Under What it should do, describe the outcome. This becomes the goal's brief.
4. Optionally add files or links with + Add files or links. Files can be up to 25 MB each and 50 MB per goal.
5. Pick the Workspace, or link an existing epic instead of writing a new one.
6. Under The path, pick the recipe and check the steps. Each row says whether it holds for you or runs through, and you can change this per step.
7. Click Create goal. The sentence next to the button tells you exactly what the click will do.

An admin can change a step on the path (App feature's Decide and Plan steps) and keep the result with Save as recipe…. Saved recipes show up after the built-in ones.

Goals work with Jira, Linear or Notion, or with no tracker at all. With no tracker, the epic and tasks are internal tasks kept in Kadmo. With a tracker project but no epic yet, the button says the goal is created with no epic yet — nothing runs until one is linked.

Decide and confidence

The analysis returns one row per decision. Each row carries a recommendation and a confidence score, shown as a bar with a percentage.

• At or above the bar, the row is the agent's call and goes ahead without you.
• Below the bar, the row asks you.
• Spend, access and anything irreversible always ask you, whatever the score. So do facts only you can give and product calls.

A recommendation with no stated basis is capped at 80%, and one whose reviews disagreed is capped at 70%.

The confidence bar is set per account under Settings → General → Confidence bar. It is a whole number from 50 to 100 and defaults to 85%. Only admins can change it. Goal pages re-band their rows on the next refresh.

To answer, use Post N answers…, which shows the comment before it is posted to the epic, or Post the agent's calls… when nothing asks. ⟳ Re-analyze runs the analysis again. When nothing asks, the 10-minute window starts and the plan follows on its own: The plan starts on its own with the agent's N calls — none fell below the bar (85%).

Chats on each step

Each step has a Chats column for the questions and requests that belong to it:

Step	Starter	Button
Decide	Align open questions	Send
Plan	Propose a task	Ask PM for a ticket
Build	QA the app	Start QA job

Every item on the goal page also has an Ask pill, or Ask about <key> in its ⋯ menu. Answers can carry cards such as Apply to …, Retry with this note or Create in …. Nothing changes and nothing reaches your tracker until a person presses a card. Messages are limited to 2,000 characters, and only admins can write in a goal chat.

Each step also shows the run behind it. While it runs, you see its step ribbon and Open run ›. When it is done, you see one line with the status, duration, tokens, turns and attempt, and Show steps opens the details.

The owner

Every goal has one owner: the person the goal asks and e-mails.

• A goal you create is yours.
• An imported goal belongs to the epic's lead if they are a member of the account (in Jira the reporter, in Linear the project lead or else the creator). Otherwise it belongs to the person who imported it.
• To hand a goal over, open ⋯ → Owner and pick a member. Only the owner and admins can do this.

The owner gets an e-mail when the goal needs them, and a Slack or Microsoft Teams direct message too when their address matches. This happens when the decisions ask, a run stops, the epic could not be written, a hold is reached, Build needs them, or the goal is done. Kadmo sends at most one message per goal every 10 minutes. The bell on the goal row turns these messages off and on for that goal.

Who can do what

Action	Who
See goals	Every member of the account
Answer decisions, approve, start a held step, hand over the goal	The goal's owner and admins
Create, import, edit, delete goals; change members; write in chats	Admins

A member who tries an admin action is refused with Forbidden: admin role required.

Membership

A goal's members are the epics and issues it covers.

• Add epics / issues opens a picker to add more.
• Remove from goal in a task's ⋯ menu takes a task out. Removed tasks are listed under N removed · Show, with Put back.
• Link a label / Initiative… ties the goal to a Jira goal: label or a Linear initiative.

Membership changes stay in Kadmo and are never written to your tracker.

The Goals list

The list (app.kadmo.ai/goals) shows the goals of the workspace you are in. Tabs across the top, called the lens, filter it:

Lens	Shows
Open (default)	Every goal that has not shipped
Needs you	Goals waiting on a decision, approval or action from you
In motion	Goals with work running
Not started	Goals that have not started yet (only while there are some)
Shipped	Goals that are done or live

The lens is kept in the address (?lens=needs-you), so you can share a filtered view. Within a lens, goals are grouped in the same order: Needs you, In motion, Not started, Shipped.

Each row shows:

• the status pill, for example Decide · you or Plan · running
• the name and summary
• a tasks bar (X of Y done · N in progress)
• the owner
• the next action, such as Answer N, Start the plan, Approve N or Retry

The ⋯ menu has Holds…, Checks…, Set status…, Rename…, Edit description…, Move to workspace…, Owner and Delete goal…. Deleting a goal cannot be undone. It keeps the tracker epics and issues, the pooled tasks and the runs.

Admins see an Owners switch (Mine / All) that decides whose goals count under Needs you.

Import goals

If your account has Jira or Linear connected, you can turn existing epics into goals:

1. On the Goals list, click Import from Jira… or Import from Linear….
2. The dialog lists the epics of the projects your workspace is linked to, leaving out epics that are already in a goal. Filter by key or title. Open only is on by default.
3. Select epics and click Import N goals. You get one goal per epic, named after the epic, in the current workspace.

An imported goal starts at Decide, marked imported. Start chat opens a review of the epic's open questions.

Import needs an admin. It is not available for Notion or for internal tasks. If no workspace is linked to a tracker project, the dialog asks you to bind a workspace to a project first (see Workspaces).

Errors you may see

Message	Fix
Name the goal first — it is what the goal and its work are called.	Enter a name.
That name has no Latin letters or digits, and the goal's link is made from them — add one.	Add a letter or digit to the name.
A goal with a name like this already exists — rename this one.	Choose another name.
… is X MB — the limit is 25 MB per file.	Attach a smaller file or a link to it.
The goal's epic could not be written in …	The goal was created. Open it, then retry or link an existing epic.
Goals could not read this account's epics from …	Reconnect the tracker under Go to Integrations.
Forbidden: only the goal's owner or an admin can do this	Ask the owner or an admin, or have the goal handed to you.

Related

• Tasks: where a goal's tasks run
• Playbooks: the analysis, plan and delivery runs behind each step
• Integrations: connect Jira, Linear or Notion