Spec preview & export.
See the live spec; export it as Markdown, HTML, or PDF.
Two surfaces, one workflow: see what your spec will look like (preview), then ship it (export).
Live spec preview #
Toggle the eye icon on the right rail. The full spec renders in the right region in export form — the same Markdown that will go into the final spec.md, styled for reading.
The preview updates as you edit. Save a field on the left, the right side re-renders within a second.
What's in the preview:
- Every locked phase's content
- Every drafting phase's current content (clearly marked as draft)
- The auto-generated table of contents
- Frontmatter (title, version, generated date, AI tool target)
What's not in the preview:
- Empty / unstarted phases — they're omitted entirely, not shown as placeholders.
- Wishes, amendments, audit entries — the spec is the committed state of the project, not its discussion.
The preview is read-only. To change content, edit the underlying phase fields.
Exporting #
When P-08 (Handoff) completes, the Export action becomes available from the project header.
The export modal asks for:
- Format — Markdown (the agent-native format), HTML, or PDF.
- Title — defaults to project name.
- Author / company — optional cover-page fields.
- AI tool target — Claude Code, Cursor, Aider, or none. Tunes the document shape (e.g. file-tree examples vs prose-only).
Hit Download. The file streams to your machine. There's no cloud archive — every export is a fresh snapshot from the current project state.
What the agent gets #
A single Markdown file with YAML frontmatter, structured into sections matching the nine phases, with the supporting bundle inline:
spec.md ← the unified document
├── frontmatter ← project metadata
├── §01 Vision ← problem, users, value, scope
├── §02 Features ← stories with acceptance criteria
├── §03 Brief ← consolidated narrative
├── §04 Design ← tokens, screens, components
├── §05 Architecture ← stack, schema, contracts, folders
├── §06 Quality ← test matrix, edge cases
└── §07 Security ← threats, auth, deployment
This shape is fixed — it's the contract every supported agent expects. Changing it would break agent reads.
Re-exporting #
Every export is a snapshot. There's no version history of past exports — if you need to retain one, save the downloaded file yourself and check it into a repo. The project's audit log records each export action with timestamp, format, and operator.