Getting startedSet up integrationsCreate your first initiativeInvite your teamPlan today's workShare your first update
Spec-driven developmentAI HandoffMerge & Pull RequestsCommentsSlack Discussions
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

Spec-driven development

Spec-driven development means the initiative or bug is the implementation brief. Write it once, then send it to a coding tool, agent, or person.

Write the spec as work

For planned work, the spec is an initiative: a brief with roadmap visibility and the decisions the team should keep. For defects or incidents, the spec is a bug with enough detail for investigation and repair.

The spec should name the problem, expected outcome, and scope. It does not need to cover every implementation detail. AI coding tools and agents such as Codex or Claude Code can work through those details after launch.

When the initiative is rough, Writer Mode can turn notes about the problem, scope, proposal, and risks into a working brief. Attach Documents only when research, diagrams, demos, or design notes need their own page.

Move from spec to execution

AI Handoff is the direct path. It packages the initiative or bug for Cursor, Claude, Codex, or a terminal workflow so you choose the target, mode, and timing.

Agent orchestration is the queued path. Send the same initiative or bug to an agent profile, then a local or cloud worker can claim the session, report progress, and complete the work.

Agent workflows maps the handoff paths. Agent Sessions explains queue and claim behavior.

Connect completed tasks

When the work is finished, completed tasks are connected automatically to the initiative or bug. The spec stays attached to the result, instead of leaving the brief in one place and the update somewhere else.

Captured Work explains how completed work appears in recaps and other progress views.

PreviousBlockersNextAI Handoff

Agent Sessions

Understand how agent sessions queue work, grant claims, report progress, and finish.

Local Workers

Create and run a local Codex worker from Desktop or the CLI.

Build Cloud

Build a cloud agent that stays online and can be shared by a team.

Build Local

Build a local agent that runs on your machine and claims your queued work.

  • Write the spec as work
  • Move from spec to execution
  • Connect completed tasks
  • Back to top