Spec-driven development

In spec-driven development, the initiative or bug is the implementation brief. You write it once, then send it to an agent, a coding tool, or a person, and the result links back to it.

Write the spec

For planned work, the spec is an initiative. For defects and incidents, it is a bug with enough detail to reproduce and fix.

Name the problem, the expected outcome, and the scope. Leave implementation details to the agent: coding agents such as Codex or Claude Code work those out after launch.

If you only have rough notes, Writer Mode turns them into a brief. Attach a document only when research, diagrams, or design notes need their own page.

Send it

Select Send to... on the item and choose a workflow, an agent, or a coding tool. Send to Agents covers each option and the launch modes.

Sending to a workflow or agent queues the work. An agent picks it up and reports progress. With Git connected, it can push a branch and open a pull request. Agents & Workflows explains the options.

See the result on the spec

When the work is finished, the completed tasks are linked to the initiative or bug automatically. The brief and its result stay together. Captured work explains how completed work reaches recaps and progress views.