Documents

Documents hold durable context for initiatives, bugs, todos, and agent work. Create them in the workspace library, edit them in a dedicated editor, and link them to the work records that need the same brief.

What documents are for

Documents fit initiatives, bugs, todos, agent work, or workflow runs that need more durable context than a short description or comment thread. They can contain requirements, briefs, plans, handoffs, or supporting notes.

In spec-driven development, documents support the spec. Keep the initiative, bug, or todo as the record people assign, launch, review, and measure.

Open the documents library

Open Documents from the workspace section of the main menu. The library lists every workspace document in a grid or list.

Search by title from the toolbar. Sort by Last updated, Date created, or Title. Switch between Grid view and List view with the toolbar controls.

Create and edit a document

Select New document in the library to create one and open the editor.

The editor saves title and body changes automatically. Edit the title at the top of the page and write the body in the rich text editor below it.

The Document Details sidebar sets the document type:

Requirement
Design Doc
Spec
Research
Review
Notes

The sidebar also shows the author, created date, and last updated time. Select Delete document to remove a document permanently.

Link documents to work

From an initiative, bug, or todo detail page, the Documents strip below the description lists attached documents.

Select Add document to attach an existing document or create a new one. Attached documents appear as chips. Open a chip to edit the document. Remove a chip to unlink the document from that work record without deleting it.

When you open a document from a linked work record, the breadcrumb includes a link back to that record. The document detail page shows linked initiatives in a related table.

Workflow artifact documents

Workflow runs can attach canonical plan, review, and result-summary documents to the linked task. Each artifact type maps to one document per task, so repeated plan-build-review loops update the same records instead of creating duplicates per run.

These workflow documents use structured document-block:v1 sections for goals, requirements, review findings, and implementation notes. Agents edit those blocks through document tools during agent steps.

For artifact types, block statuses, expected inputs and outputs, and the review feedback loop, see Workflow Reference.

Rich context in work

Long-form descriptions give an initiative, bug, or todo enough context for someone to act without hunting through other tools. The editor supports structured text, links, YouTube embeds, Figma embeds, Mermaid diagrams, code blocks, task lists, and uploaded media.

Keep the most important decision, requirement, or reproduction detail near the top. Put supporting demos, designs, diagrams, and notes below it so the record stays scannable.

A walkthrough of adding demos, designs, diagrams, and structured context directly to work.

How documents connect

Documents can support AI Handoff when the assistant needs the same brief, design, or decision log a person would read. Agent setup starts with choosing how agents run and Building Workflows; API details belong in Developers.

Reference

Reference workflow definitions, execution, step types, task modes, artifact documents, and agent responsibilities.

Overview

Understand when to use workflows, direct agent assignment, apps, or terminal handoff.

Bugs

Capture defects with the detail needed for triage, ownership, and repair.

Initiatives

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