Initiatives
Initiatives are planned work with enough shape to stay visible on the roadmap. They carry the brief, ownership, hierarchy, taxonomy, and status used for planning, delivery, updates, and measurement.
For workflow guidance, start with Initiatives & Bugs or Roadmap.
Fields
Initiative fields make larger work comparable and reviewable.
| Field | Purpose |
|---|---|
| Description | The problem, scope, proposal, risks, and decisions. |
| Owner and assignees | Who is accountable and who contributes to the work. |
| Teams | Where the initiative appears for planning, standups, updates, and analytics. |
| Status | Whether the work is an idea, planned, in review, blocked, completed, or cancelled. |
| Priority | A ranking signal for roadmap work that needs ordering. |
| Planning | The planning state used when the initiative moves into roadmap work. |
| Parent initiative | The larger initiative this work belongs under. |
| Taxonomy | Goals, companies, products, skills, coding tools, or agents connected to the work. |
| Created at | When the initiative record was created. |
| Updated at | When the initiative was last changed. |
| Completed at | When the initiative was marked completed, when that applies. |
Initiative detail panels and the roadmap sidebar show Created at, Updated at, and Completed at after ownership and taxonomy fields.
Initiative detail page
The initiative detail page shows the brief, fields, taxonomy, comments, and attached documents in the main column.
Reference tabs
Tabbed sections below the brief organize related work:
| Tab | What it shows |
|---|---|
| Related | Parent, sibling, and child initiatives around the open record, grouped by relationship. |
| Journal | Completed tasks linked to the initiative. |
| Changes | Pull requests, branches, and commits linked to the initiative or its descendant work. |
| Insights | Scoped work metrics for the open initiative and its related completed work. |
The Related tab groups initiative hierarchy:
| Group | What it shows |
|---|---|
| Parent Initiative | The initiative this work belongs under. |
| Sibling Initiatives | Other child initiatives under the same parent. |
| Child Initiatives | Initiatives nested under this record. |
Each row shows status and title. Select a row to open that initiative's detail page. Active initiatives appear before completed ones. Tabs with no linked work stay disabled.
Insights tab
The Insights tab summarizes work tied to the open initiative, including completed child tasks and nested initiative work. Metrics reuse the same definitions as workspace Insights, scoped to the selected record instead of the full workspace or team view.
Cards appear when matching data exists:
| Card | What it shows |
|---|---|
| Local agent tokens | Token usage from local agents, with input and output split when available. |
| Work type | Mix of frontend, backend, infra, docs, bug fix, feature, and refactor work. |
| Lines changed | Total lines changed, with insertions and deletions when available. |
| Contributors | People who contributed to the scoped work. |
| Skills | Top skill labels on the scoped work. |
| Coding tools | Top coding tool labels on the scoped work. |
| Agents | Agent labels or captured agent session usage. |
| Activity | Sparkline of completed work over recent days. |
When no scoped metrics exist yet, the tab shows No work insights yet. Individual cards stay hidden when their metric is missing.
Breadcrumb navigation shows the parent initiative chain when you open a nested initiative. Each ancestor links back to its detail page.
Agent runs linked to the initiative appear below the tabbed sections. For pull request review workflows, see Merge & Pull Requests.
Hierarchy
Initiatives can be nested. A large initiative can have child initiatives under it, and the roadmap table shows the tree with child work indented under the parent.
Parent initiatives can show progress based on completed or cancelled descendants. Completed and cancelled child initiatives stay closed when a parent changes status.
Roadmap table
The roadmap table can search, filter, group, and inspect initiatives. Filters can include assignee, team, status, kind, product, customer, goal, and skill. The assignee filter includes Unassigned so teams can find roadmap work without a clear owner.
Grouping can split initiatives by owner, assignee, team, product, customer, goal, or skill. Initiatives with several matching taxonomy terms or teams appear in each matching group.
Actions
Initiatives can be created, edited, deleted, duplicated, merged, reordered, reparented, bulk updated, and bulk deleted. They can also be converted between initiative and ongoing work when the shape of the work changes.
Planned initiatives can be stack ranked when they do not have planned child initiatives.
When a completed initiative should also appear in Daily recap and the Journal, completed-work behavior is controlled by Preferences. The complete capture model is explained in Captured Work.