Todos

Todos are for simple day-level work owned by one person.

Create an Initiative when the work needs shared context, a roadmap link, hierarchy, or a brief. Create a Bug when the work is a defect. Use a todo when the work is small enough for one person to finish and report without a broader planning record.

In spec-driven development, a todo can be a small personal spec. Keep it short. If it needs a real brief, move the work into an initiative or bug before handing it off.

Journal

The Journal is the chronological record of completed tasks and captured work. Use it when the daily recap is too narrow and you need to review what shipped across previous days or months.

Planned todos appear at the top so upcoming work stays visible. After you finish one, the Journal records the result as a completed task. Completed tasks can also come from captured tool activity, agent work, or finished initiatives.

Add completed work manually

Use the Journal create action to add completed work manually.

For work that is not finished yet, create a todo and move it through planned, in progress, or blocked states.

Todo fields

A todo can carry status, parent initiative, visibility, owner, assignees, reviewer, reporter, team assignments, completion date, deadline, taxonomy, linked work items, and a long-form description.

Keep todo descriptions short. If the explanation turns into a brief, split the work into an initiative or bug so the team can plan, review, and measure it correctly.

Todo actions

Todos support direct links, detail panels, comments, threaded replies, reactions, reassignment, snoozing, bulk updates, split, merge, deletion, and Slack discussion.

Visibility controls whether a todo is private to you or shared with the team. Use team visibility when the todo needs to appear in planning, standups, reports, and shared review.

Every todo can be handed to an assistant through AI Handoff. For queued agent execution, use Agent Sessions.