Cross-document workflows
One-click workflows that turn a source document into a linked set of follow-up documents, like epics and user stories planned from a PRD.
Some documents naturally lead to others. A PRD becomes epics and user stories. A business case becomes OKRs. Cross-document workflows do that chaining from the document you are looking at.
Run a workflow
- Open a document that has a workflow (today: a PRD or a business case).
- Click Workflows in the document header, then pick the workflow (for example Create Epics and Stories).
- For a PRD, ForceVue first reads the document and plans the breakdown: which epics, and which stories under each. The confirmation shows that real plan, with the exact total ("This will create N documents"), before anything is generated.
- Click Create N documents to start, or Cancel to back out. Cancelling writes nothing (the planning step has already run, and that is the only quota spent).
Each document is a normal document generation: it reads the same initiative context, goals, related documents, and uploads as the Generate dialog, and carries the same source attribution. While the chain runs, the dialog shows per-step progress with stories nested under their epic. Every finished document is usable right away, with an Open link next to it; you do not wait for the whole chain.
The two built-in workflows
| Source document | Workflow | Creates |
|---|---|---|
| PRD | Create Epics and Stories | A planned set of epics and user stories (up to 5 epics, up to 25 stories each, 30 documents total) |
| Business case | Create OKRs | 1 OKRs document |
Every document the workflow creates is linked back to the source with a Derived from reference, and each story is also linked to its parent epic, so you can trace the chain from any document's references panel.
How long a big breakdown takes
Documents are generated several at a time, so a large breakdown does not run one document after another. Epics are written first (they are what stories hang off), then the stories. A full 30 document breakdown takes on the order of ten minutes; smaller ones finish much faster. The dialog shows an estimate before you start and again while it runs.
A run that big is more than one server request can hold, so the workflow continues itself and the progress list keeps ticking. You do not need to do anything, and nothing is generated twice. If a request is cut short, the run picks itself back up.
Continue generating appears only if the run cannot recover on its own. Everything already created is saved, and continuing picks up only the steps that never ran.
If a step fails
A failed step stops the run. Documents that were already created stay put, and the dialog plus a toast tell you which step failed and why. Nothing retries on its own; you can fix the cause (for example, wait out a rate limit) and run the workflow again when you are ready. If the planning step itself fails, the dialog says so and nothing is written or charged.
Workflows spend quota like manual generation
Every document a workflow creates counts against your monthly AI generation allowance and your per-minute rate limit, exactly as if you had generated each one yourself. The planning step counts as one generation too, so a five-document workflow costs six in total.
Where to go next
- Generating documents for the single-document flow.
- How generation works for what the AI reads.
- Usage and limits for quotas and rate limits.