A few suggestions for improving Figma Specs for PRD workflows
I've recently started trying out Figma Specs for writing PRDs alongside my designs. I really like the direction this is going. Having requirements and designs in the same place could save a lot of time, especially when working on complex enterprise products.
After trying it out, there are a few things I feel are missing.
1. A table of contents
This is the first thing I noticed. Specs supports headings, but there's no document outline or table of contents, even in full-screen mode.
For a longer PRD with multiple sections, it's difficult to navigate without scrolling through the entire document.
It would be useful to have a collapsible sidebar that automatically lists headings and lets you jump between sections.
2. Revision history and change notes
PRDs change frequently during reviews and development.
I'd like to be able to add a short note when making changes, explaining what was updated and why. It would also help to compare versions, see who made changes, and restore an earlier version when needed.
Regular comments are useful for discussions, but they're not quite the same as keeping a record of requirement changes.
3. Better links between Specs and designs
Being able to reference Figma designs inside Specs is already useful, but I'd love to see this go further.
For example, clicking a field in a design could take me directly to its requirement description in Specs, and vice versa.
It would also be helpful to know which requirements or screens might be affected when something changes.
4. A simple review and approval workflow
When working with developers and stakeholders, it's important to know whether a PRD is still being drafted, under review, or approved.
A simple document status, review history, and the ability to mark an approved version would make collaboration much easier.
5. Reusing requirements across Specs
In enterprise applications, different modules often share the same business rules, such as permissions, validation rules, and status definitions.
It would be great to reference a shared requirement from multiple Specs without copying and maintaining the same content in different places.
6. Better tables and document export
PRDs often contain field definitions, permission matrices, and state transition tables. More flexible table editing would be helpful.
Exporting to Word or PDF while preserving the document structure would also make it easier to share requirements with customers and teams that don't use Figma.
I know Specs is still evolving, and I don't expect all of these features at once.
For me, the biggest priorities would be a table of contents, revision tracking, and better connections between requirements and designs.
I think these would make Specs much more practical for day-to-day product management work, rather than just keeping documentation next to designs.