Collaborate on drafts — AI Prompts for Notion

The four heights

The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.

Execute — do the immediate task

We have a draft product spec that three people must edit: Aisha, Ben, and the engineering lead,…

We have a draft product spec that three people must edit: Aisha, Ben, and the engineering lead, Clara. Put the spec into a shared document, invite those three as editors, add an inline comment at the top asking reviewers to focus on acceptance criteria, and lock the title and structure so authors don’t accidentally rename sections. Set a one-week review window ending next Friday and notify everyone with a short task assigning who reviews which sections.

Improve — make it easier to accept

Before we open this spec for collaborative edits, make it easy to give useful feedback: surface a…

Before we open this spec for collaborative edits, make it easy to give useful feedback: surface a short checklist at the top—scope, acceptance criteria, non-goals, dependencies—make each reviewer’s section visible and labeled, and add a Review Needed tag so editors know this file is in the current sprint review. Flag any paragraphs longer than four sentences for simplification.

Decide — diagnose the stuck moment

I posted a product spec and Aisha says the scope is too narrow while Ben expanded it in comments.…

I shared the draft and received conflicting comments from Aisha and Ben on scope.

I posted a product spec and Aisha says the scope is too narrow while Ben expanded it in comments. Clara hasn’t weighed in yet. I’m afraid if I lock the scope now I’ll alienate Aisha, but if I leave it vague we’ll waste engineering time. I can’t tell which changes reflect new customer needs and which are personal preferences. What’s the quickest way to resolve scope tension and get Clara to decide?

Become — change the pattern

We repeatedly open docs for review and end up with overlapping, unresolved comments that push work…

Drafts sit in review for days with scattered comments, delaying engineering.

We repeatedly open docs for review and end up with overlapping, unresolved comments that push work back a sprint. Reviewers assume someone else will consolidate feedback. What single review ritual or document habit will make reviews decisive, reduce review duration, and ensure comments are resolved before engineering starts?

Next to this one

Other docs and databases work people do in Notion.

Assign recurring tasks Build interview notes Build personal journal Build product roadmap Capture quick ideas Collect application submissions Collect research sources Create CRM records Create habit tracker Create kanban boards

Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.

The rest of the map

Same library, five ways in.

Work Atlasthe whole map, interactive Careers1,949 jobs and their real tasks Soft skillsthe human part of the work Activities500 things people do Prompt Librarybrowse every prompt