Post-Kickoff Scope Creep — AI Prompts for Adobe Acrobat

The moments that lead here

If one of these is your afternoon, you are in the right place.

sitemaps keep growing after kickoff and devs get pulled into scope debates.

1 ready prompt

Written for the moment this actually comes up.

Become — change the pattern

Across the last five projects, where do sitemaps morph into extra features during development?…

Across the last five projects, where do sitemaps morph into extra features during development? Diagnose whether the issue is missing business-mapped pages, stakeholder ambiguity, or our vague annotations, and recommend one lightweight sitemap convention that prevents scope creep and keeps devs focused on MVP.

Who does this, and with what

The same task is different work inside a different job.

Web DesignerAdobe Acrobat

Next to this one

Other convince work people do in Adobe Acrobat.

Persuasive Accessible Brief Persuasive Lender Packet Persuasive Report Style Pitch-Risk Messaging Gap Portfolio-Wide Repricing Rationale Prefill Adoption Resistance Prefill Recurring Fields Prep Dossier For Inspection Prep Inspector Binder Pages Prepare Accessible Documents

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