Living Documents
Your product model already holds the structured truth — Features, Rules, Flows, Metrics, and the decisions behind them. Living Documents turn that graph into the prose artifacts people still expect to read: a PRD, a one-pager, a brief, or release notes — narrated automatically from the current state of the model.
Because they’re generated from the graph rather than hand-written, Living Documents don’t drift the moment the product changes: Specor tracks when the underlying nodes move on and flags the document as stale, so you never circulate an out-of-date spec.
Document types
| Document | What it narrates |
|---|---|
| PRD | A full product requirements document for a Capability or Feature area — needs, features, rules, flows, and success metrics |
| One-pager / Brief | A concise summary of a slice of the product for stakeholders |
| Release notes | What changed between two points in your product’s history |
Generating a document
- Open the Documents view
- Choose a document type and the part of the graph it should cover (for example, a Capability and its Features)
- Specor narrates a draft from the current model — review and edit it
Generating a document is a generative AI action, so it draws on your plan’s AI credits (unlike the always-free proactive checks).
Staleness tracking
Once generated, a document stays linked to the nodes it was built from. When those nodes change — a rule is edited, a feature is added — Specor marks the document stale and shows what moved, so you can regenerate it in one step instead of hunting for what’s out of date.
Documents and the source of truth
Living Documents are outputs, not the source of truth — the graph is. That’s the inversion that keeps them honest: instead of a document that slowly diverges from reality, you have a model that stays current and documents that are re-rendered from it on demand.
Tips
- Generate late. Produce a PRD or release notes once the relevant part of the model has settled, so the narration reflects the real, current state.
- Let staleness drive updates. Rather than proactively rewriting docs, wait for the stale flag and regenerate — it’s faster and never misses a change.
- Pair with history. Release notes are most useful generated between two points in your history.