Exporting a PRD

Once your PRD is generated, you can export it in three formats. Each format is suited to a different downstream use case.

Export options

After generating a PRD, three export buttons appear at the top of the PRD panel.

Copy Markdown

Copies the full PRD as raw Markdown to your clipboard.

When to use: Pasting directly into an AI coding tool (Claude Code, Cursor, Lovable) or into a document editor that supports Markdown (Notion, Linear, GitHub Issues).

Format: Standard Markdown with ATX headings (##), bullet lists, and code fences for technical sections.

Tip for AI tools: Paste the Markdown into your coding tool and prepend:

Build the application described in the following PRD.
Follow the tech stack and architecture decisions exactly.
Do not deviate from the acceptance criteria.

This framing consistently produces better results than pasting the PRD without instruction.

Download PDF

Downloads a formatted PDF file of the PRD.

When to use: Sharing with stakeholders, investors, or contractors who need a polished document. Keeping a record outside the platform.

Format: A rendered PDF with typography, headings, and layout applied. Code blocks and tables are formatted for readability.

File name: [project-name]-prd-v[version].pdf

Download JSON

Downloads the PRD as a structured JSON file.

When to use: Integrating with your own tooling, processing the spec programmatically, or feeding it into a custom agent pipeline.

Format: A JSON object where each top-level key maps to a PRD section (camelCase), and the value is the section content as a string. For example:

{
  "executiveSummary": "...",
  "targetUsers": "...",
  "technicalArchitecture": "...",
  "featuresAndRequirements": "..."
}

File name: [project-name]-prd-v[version].json

MCP Export (coming soon)

MCP Export will allow you to push your spec directly to AI coding tools via the Model Context Protocol — no copy-paste required.

Your canvas becomes the agent's instruction set. When an agent opens a task, it receives the full structured spec as context before writing a single line of code.

Planned targets:

• Claude Code
• Cursor
• Lovable

Exporting older versions

Export is not limited to the most recent generation. From the History tab:

1. Click any previous version to open it.
2. The same three export buttons appear.
3. Export the older version as Markdown, PDF, or JSON.

This is useful for comparing what was specced at different stages of the project or for providing a client with a snapshot from a specific date.