Docs

The Docs tab is where long-form writing lives — product requirements, technical specs, project notes, anything that doesn’t fit in an Issue card. Docs are stored alongside your codebase and can be attached to AI chat sessions so the agent reads them as context every turn. Open it from the Docs icon in the left sidebar.

​

What you can write

• PRDs — product requirements for a feature.
• Specs — technical designs, RFCs, architectural notes.
• Project notes — meeting notes, decision logs, scratchpads.

Every doc is markdown under the hood, with a rich editor on top. You get headings, lists, code blocks, callouts, images, and inline links to other docs, issues, and canvases.

​

How docs connect to the rest of Tempo

A doc on its own is just a document. The point is to link it to the work it describes:

• Link a doc to a chat session and the agent loads it into context every turn — so when you ask “implement the spec,” it actually has the spec.
• Link a doc to an Issue and the card shows the PRD inline.
• Link a doc to a canvas so the design surface and the requirements live next to each other.

​

Drafting with AI

You can draft a PRD interactively by asking the AI: “write a PRD for the export-to-CSV feature.” The /prd-writer skill walks through the structure (goals, non-goals, user stories, success criteria) and writes it directly into the Docs tab.

​

Where docs live

Docs are stored in your organization’s database, scoped to the workspace they were created in. Teammates in the same organization see the same docs; private workspaces stay private.