Getting startedSet up integrationsCreate your first initiativeInvite your teamPlan today's workShare your first update
StatusesWork TypesSearchCaptured WorkInitiativesBugsIdeasTodosDocumentsWriter ModePermissionsNotification TypesTaxonomy TypesTriage ItemsGlossary
DocsAPI Reference

Main

  • Home
  • About
  • Pricing
  • Vault
  • Changelog
  • Docs

Features

  • Roadmaps
  • Planning
  • Standups
  • Status updates
  • Insights
  • AI assistant / MCP
  • Integrations

Solutions

  • Startups
  • Dev shops / agencies
  • Software teams
  • Internal IT & platform teams

Alternatives

  • vs Jira
  • vs Linear
  • vs Asana
  • vs Monday.com
  • vs ClickUp
  • vs Notion

Company

  • Blog
  • Security
  • Log in
  • Sign up
  • Terms of Use
  • Privacy Policy

Resources

  • Docs
  • Community
  • API reference
  • CLI
  • Desktop app
  • SDK

© 2026 One Horizon. All rights reserved

FacebookInstagramThreadsXRedditTikTokYouTubeMedium


Todos

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

Create an Initiative for work that needs shared context, a roadmap link, hierarchy, or a brief. Create a Bug for a defect. Create a todo only 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.

Infrastructure
Plan cloud infrastructure expansion

Journal

The Journal is the chronological record of completed tasks and captured work. Open it when 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

The Journal create action adds 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 lightweight planning detail.

FieldPurpose
StatusShows whether the todo is planned, in progress, blocked, or completed.
Parent initiativeKeeps small personal work connected to larger planned work.
VisibilityControls whether the todo is private or visible to the team.
Owner and assigneesShow who is responsible for the work.
TeamShows where shared todos appear for team planning and updates.
Completion datePlaces finished work in the Journal and recap.
DeadlineMarks time-sensitive personal work.
Taxonomy and linked workConnects the todo to reporting or source activity when that matters.

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 the same small-work flow across planning, discussion, and delivery. You can open a detail panel, comment, reassign, snooze, split, merge, delete, or start a Slack discussion.

Visibility controls whether a todo is private to you or shared with the team. Team visibility makes a todo 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.


PreviousIdeasNextDocuments

Initiatives

Understand initiative fields, hierarchy, roadmap behavior, and initiative actions.

Writer Mode

Writer Mode turns rough initiative context into a structured working brief.

Captured Work

Understand how connected activity becomes completed tasks, recaps, insights, and attribution.

Triage Items

Understand triage reviewers, decisions, duplicate handling, and backlog outcomes.

  • Journal
  • Add completed work manually
  • Todo fields
  • Todo actions
  • Back to top