Skip to main content

How to use documents

Documents are where you put your product thinking to paper. Use them to write PRDs, specs, strategy docs, briefs, or any long-form artefact that captures context your team and coding agents need. Documents live in a planning session alongside tasks and chat, so everything you write stays connected to the conversation and the work it generates.

Creating a document​

You can prompt your way to writing docs (for example, "write a PRD for this" or "draft a spec for the onboarding flow"), or go freeform.

Each session can hold multiple documents, appearing as tabs above the editor.

Editing a document​

Documents are fully editable, either by typing directly or prompting your way to making edits. Your whole team can see and can edit the same doc. You can highlight a passage and ask Rezonant to improve, shorten, or restructure just that section. For larger rewrites, describe what you want and Rezonant will handle the redraft.

Document templates​

When you ask Rezonant to draft a document, it picks a template based on what you're trying to create. Templates give documents a consistent structure so nothing important gets missed.

  • PRD (Product Requirements Document) - For capturing a problem, the goals behind it, user stories and requirements, success metrics, and open questions. Use this when you're defining a new feature or initiative, and you need a structured artefact to align stakeholders or brief your team.
  • Spec (Technical Specification) - A more technical document for when you know what you're building and need to nail down how you're going to do it. It normally covers the proposed solution, architecture, rollout plan, validation approach, and a detailed implementation plan. Well-suited to handing off to engineering or a coding agent.
  • Strategy - For stepping back from individual features to document direction: what you're optimising for, the choices you're making, and why. Useful for team alignment, roadmap planning, or capturing a decision that needs a paper trail.

If none of the templates fit, Rezonant will write freeform based on what you asked for. You can rewrite the document in a different template with the 'Auto' button in docs. You can edit and add more template styles under 'Templates' in the homescreen menu.

Turning documents into tasks​

Once a document is in good shape, you can ask Rezonant to break it down into tasks. Rezonant reads the document alongside the conversation and any linked codebase to generate structured, context-rich tasks ready for your engineering team or a coding agent. You don't need to copy anything across - the session keeps it all connected.

Exporting and syncing documents​

Documents can be exported as markdown files or copied as rich text to paste into any external tool. If your workspace is connected to a document repository, such as Notion or Confluence, you can push a document there directly.

For teams using Jira or Linear, documents don't export directly to those tools, but the tasks generated from them do. The document stays in Rezonant as the living context behind the work, while the tasks travel to your tracker.