The gaps in an idea note are the useful part
Ideas arrive as a paragraph in a message. The paragraph contains a solution, usually a screen, and rarely the problem it solves or the way anyone would know it worked.
A requirements document that fills those gaps by inference is worse than no document, because the invented scope gets built. The honest version separates what the note said from what it did not say, and places the second list where the author will see it.
Success measures suffer most. Asked for one, generation produces a plausible-sounding metric nobody can query. A team then spends a quarter working toward a number that was never real.
A draft is the right artifact here. Structure is cheap to produce and tedious to write. Judgment about scope stays with the person whose idea it is.
How the ActionFlow runs on the canvas
An idea note arrives through a Start node or from Slack. A Notion node supplies your product document template so the draft matches what your team already reads.
A Generate Object node returns the note split into problem, proposed solution, scope, out of scope, and success measure, with every section marked as either stated in the note or absent from it.
Explicitly marking absence is the design decision here. A section written from inference and a section quoted from the author look identical once the document is formatted.
A Filter node collects the absent sections into a question list, phrased as questions rather than as empty headings.
A Generate Text node writes the stated sections into your template's prose, leaving the absent ones visibly empty with their question underneath.
A Google Docs node holds the draft for the author to complete. A Notion node files it against the product area.
A Slack node returns the question list to the author directly, because the questions are the part that needs an answer before anything else is worth writing.
Nodes this ActionFlow uses
- Start (Start) with Slack (Communication): the note as it actually arrives.
- Notion (Integration): supplies your product document template.
- Generate Object (AI Core): splits the note and marks each section stated or absent.
- Filter (Data): collects the absent sections into a question list.
- Generate Text (AI Core): writes only the stated sections into the template.
- Google Docs (Integration): the draft the author completes.
- Notion (Integration): files the draft against its product area.
- Slack (Communication): returns the questions to the author first.
Frequently asked questions
Start building AI workflows
Create a free account, open a template or a blank canvas, and run your first ActionFlow.
Newsletter
Get product updates
New nodes, agents, and product notes. We send mail only when we have something worth opening.