Flocci Library
Home › Solutions › Product specs
Use case · Product specs

Product spec and PRD documentation tool

A spec is only useful if the argument about it is attached. Flocci Library keeps PRDs as pages with tables and native charts for the numbers, threaded comments with @mentions for the review, @mention chips linking related specs, and a cross-app link to the Flocci Projects issue that implements the work.

Review is the part most tools get wrong: feedback ends up in a chat thread that dies, leaving the spec silently outdated. Threaded page comments keep the argument next to the sentence that caused it, and mentions pull the right person in without leaving the page.

The numbers belong in the document. Insert a table for the requirement matrix and a bar, line, pie or area chart for the usage or funnel data that motivates the work — no screenshot of a spreadsheet that goes stale the moment the query changes.

Then close the loop with execution: link the Projects issue to its spec page. Because both apps sit on one backend with a shared link graph, the connection is a real row, so the issue always points at the current spec rather than at a URL someone pasted in March.

How to set it up

  1. One space for Product; a page per initiative with child pages per spec.
  2. Open every PRD with a 40–60 word summary — that is what people actually read.
  3. Put requirements in a table and evidence in a chart block.
  4. Run review in threaded comments with @mentions, not in chat.
  5. Link the implementing Projects issue so the spec and the work stay tied together.

Frequently asked questions

Can two people edit a spec at the same time?

Concurrent editing is protected rather than merged: auto-save carries a version header, and a stale write is refused with a conflict warning instead of silently overwriting a teammate's paragraph. Live cursor-level co-editing is not shipped.

Can I put charts in a spec?

Yes — bar, line, pie and area charts are native block types inserted from the slash menu, alongside tables. Most team wikis require an external embed or a screenshot for this.

Related use cases

Internal wiki software your team will actually use

Internal wiki

Engineering documentation that stays close to the code

Engineering docs

SOP documentation software for small and mid-size teams

SOPs

Start writing in Flocci Library

Personal spaces are free — the full editor, backlinks, search, share links and free monthly AI credits. Organisations are ₹49 a seat.

Get started free