Work Types
Work Types define the objects used to 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. |
During rollout, decide whether this workspace is the main planning system or a layer beside an existing issue tracker. Native records are managed here. Synced issues keep status, priority, assignment, and visibility in the source tool until the team chooses to move ownership.
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 implementation spec a person, coding tool, or agent builds from. Completed-task behavior is covered in Captured Work.