Attachments
Specs rarely stand alone. There’s a whiteboard from the session that shaped them, a design file, a page of research — material that belongs with the document or discovery board, without being part of its content.
Attachments hold that link. A document or discovery board can carry any number of attached links; they sit with the artifact’s controls, and attaching one never changes the content itself.
Attach a link
Click the paperclip — at the top of a document, or beside a discovery board’s actions — and paste a URL.
If the link is from a supported tool (below), it opens in place the moment it attaches — no second click to discover what an attachment can do. Plain links attach quietly.
The attachment is named automatically when the linked site shares a name (a page’s title, a board’s name); otherwise it shows the link itself. Some tools keep names private from the outside — a private Miro board, for example, appears simply as “Miro board”. A link that turns out not to lead anywhere is rejected with an explanation rather than becoming a dead attachment.
Each attachment appears as a small icon; hover it to see its name.
Open an attachment
Links from supported tools open in place: the linked artifact replaces the page’s content, live, with a slim bar above it to go back to the document or board (the browser’s back button works too) or open the artifact in its own tab. Everything else opens in a new tab.
Currently supported:
- Miro boards — the actual whiteboard, editable and multiplayer, teammates’ cursors and all. A link that points at a specific frame opens the board at that frame.
- Figma files and prototypes, and FigJam boards — publicly shared files render in place; Figma only embeds public files, so a private file shows Figma’s own notice instead.
- Loom videos, YouTube videos, and Zoom cloud recordings — the player, in place. A passcode-protected Zoom link asks for its passcode right there.
- Canva designs and Sketch documents.
- Published Lovable and Bolt sites — the live published app
(
yourapp.lovable.app/yourapp.bolt.host). Paste the published address: the editor link (lovable.dev/projects/…,bolt.new/~…) has nothing to show, and the paste is declined with directions. - Google Docs, Sheets, and Slides — shown with your own Google sign-in in Chrome. Safari and Firefox block the third-party cookies the embedded viewer needs, so there they show Google’s sign-in prompt instead of the document, and the way through is the bar’s open-in-new-tab control.
In every case the embedded view follows the tool’s own permissions: with access you get the artifact; without it, the tool’s own gate or notice — and the bar’s open-in-new-tab control is always there as the way through.
Want another tool to open in place? Tell us at support@dotrequirements.io.
Remove an attachment
For links that open in place, removal lives inside the opened view — the small icons only ever open, so a stray click can’t delete anything. For links that open in their own tab, ask the assistant to remove the attachment. Either way, removing an attachment removes the link only; whatever it pointed to is untouched.
Attachments are part of the spec, wherever it goes
A document’s attachments travel with it. Pull the spec into a repository with
the CLI and the links are right there in the file — so a
developer reading the requirements in their editor can open the same
whiteboard the spec came from. An attachment added on either side is carried
to the other on the next sync, and attachments never hold up the rest of the
spec — requirements keep syncing whatever the links are doing. When the file
and the app name the same link differently, the file’s name wins. Like
everything else in additive sync, removals only propagate when one side is
given authority (--repo-wins / --cloud-wins);
to remove every attachment from the file’s side, leave an explicit
attachments: [] rather than deleting the key — a file without the key
simply has nothing to say about attachments:
---
document:
attachments:
- url: https://miro.com/app/board/uXjVHNL-KXU=/
title: Checkout flow mapping
---The assistant and attachments
Ask the assistant to attach a link and it will. If it creates something for you in a connected tool — a Miro board sketched from a spec, say — that new artifact isn’t attached automatically: ask it to attach it (or paste the link yourself) to keep it with the document or board it belongs to.