Documents

Documents hold requirements, briefs, plans, handoffs, and notes that need more room than a description or comment thread. Create them in the workspace library and link them to the initiatives, bugs, and todos that need them.

In spec-driven development, documents support the spec. The initiative, bug, or todo stays the item 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 without deleting it.

When you open a document from linked work, the breadcrumb links back to it. 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 documents instead of creating duplicates per run.

These documents are made of structured sections, such as goals, requirements, review findings, and implementation notes, that agents update during their steps.

For artifact types, block statuses, expected inputs and outputs, and the review feedback loop, see the custom agent reference.

Rich context in work

Descriptions on initiatives, bugs, and todos can hold rich content too. 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.

Documents in agent prompts

When you hand an item off with Send to Agents, its prompt includes each linked document's title and a short excerpt.