Design Naming And Retention — AI Prompts for Adobe Acrobat

The moments that lead here

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

engineers asked for a clear naming and retention scheme for design specs before sprint planning.

1 ready prompt

Written for the moment this actually comes up.

Decide — diagnose the stuck moment

Developers get confused about which spec is authoritative and I need to define retention and naming…

Developers get confused about which spec is authoritative and I need to define retention and naming rules before sprint planning tomorrow. I worry my rules will be ignored. Propose a naming convention and retention policy that engineers will accept, one place to store the authoritative versions, and a short justification I can give to get buy-in from the dev lead.

Who does this, and with what

The same task is different work inside a different job.

Web DesignerAdobe Acrobat

Next to this one

Other record work people do in Adobe Acrobat.

Deploy Retention Naming Deploy Retention Workflow Design Audit Trail Design Branded Template Design Data-Driven Stamps Design Session Plan Develop Retention Rules Digitize Complex Diary Urgently Digitize Fragile Diaries Digitize Paper Forms

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