Documents
Documents keep important context attached to initiatives, bugs, agent work, team knowledge, or todos.
What documents are for
Documents fit initiatives, bugs, todos, or agent workflows 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.
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.
How documents connect
Documents can support AI Handoff when the assistant needs the same brief, design, or decision log a person would read. Agent and API details belong in Agents and Developers.