Work Types
Use Work Types to distinguish the objects used to define, plan, deliver, share, and measure work.
Main types
| Type | Meaning |
|---|---|
| Initiative | Planned work such as a feature, project, product bet, or roadmap commitment. |
| Ongoing work | Recurring or operational work that needs ongoing visibility without a fixed end. |
| Bug | A defect that needs triage, ownership, and repair. |
| Idea | Early candidate work that is not planned yet. |
| Todo | Simple personal work that is planned, in progress, or blocked. |
| Completed task | Finished work shown in the Journal, recaps, standups, reports, and measurement. |
| Issue | Work imported or synchronized from issue trackers such as Jira, Linear, GitHub, or GitLab. |
| Pull request or merge request | Code review and merge work from connected version control tools. |
| Agent session | Queued AI work claimed and executed by a worker. |
| Document | Structured context linked to an initiative, todo, or workspace workflow. |
The distinction between native records and synced issues matters during rollout. Native records are owned here. Synced issues keep their source issue tracker as the owner for status, priority, assignment, and visibility unless the team intentionally migrates that work.
Todos are for unfinished personal work. Completed tasks are finished work. They can come from work that started as a todo, initiative, bug, captured tool activity, agent work, or manual Journal entry.
In spec-driven development, an initiative, bug, or todo can become the source context a person, coding tool, or agent builds from.
Work types become actionable through Statuses, Initiatives, and Todos. For initiative drafts, see Writer Mode.