Project management resumes drift toward methodology — a stack of frameworks, tools and ceremonies that would describe anyone in the field. What separates yours is the shape of the work: budget, scope, timeline, and the people you had to keep aligned. These prompts write from those four and ask you for the rest.
Want a finished document to work backwards from? There is a full project manager resume example in Markdown you can copy into the editor.
Before you paste any of these
Give every project a size and a shape — Budget band, team size, duration, number of workstreams, and whether it was a new build, a migration, an integration or a recovery. Ask the AI to open each project with that line, so a reader can tell a 6-week internal tool from an 18-month platform migration without guessing.
Say who you had to move, not who you reported to — Vendors, a steering committee, engineering leads, legal, a client sponsor, a works council. Ask for bullets that name the group and what alignment actually took — a re-baselined plan, a scope trade you negotiated, an escalation you carried to a decision and closed.
Cap the acronyms at a single line — Tell the AI to keep methodology to a single line — Agile, Scrum, SAFe, waterfall, hybrid — with your certifications beside it exactly as you hold them, PMP, CSM, PMI-ACP or PRINCE2, and to spend the rest of the page on the work. A resume assembled from frameworks reads much like every other one in the stack.
Get the recovery story on the page — Ask the AI to prompt you for a project that slipped and what you changed about it. Then have it write that as a bullet with [X] placeholders for weeks recovered or budget held, and tell it to leave those brackets alone until you fill them in yourself.
3 prompts to copy
Every prompt ends with the same rules: use only what you give it, and mark a missing number with a placeholder instead of guessing one.
Your bullets read like a certification syllabus and a reader still cannot tell what you delivered. Use this to push the framework down to one mention and the delivery to the front
What to have ready
•4 to 8 experience bullets from your resume
•One line per project on what actually shipped or changed, and who it affected
•The methodology terms the job posting itself uses, if any
You are editing resume bullets written by a project manager. Work only from what I paste. Do not add budgets, dates, team sizes, or results I have not given you.
My current bullets:
[PASTE 4 TO 8 BULLETS]
What actually shipped or changed on each project, and who it affected:
[PASTE ONE LINE PER PROJECT]
The methodology terms the posting uses, if I have them:
[PASTE OR WRITE "none"]
Rules for the rewrite.
- Methodology is context, not the achievement. Across the whole section, keep at most one mention of the framework I worked in — Scrum, Kanban, stage gate, waterfall, hybrid. Cut the rest. If I gave you the posting's terms, use its wording for that one mention rather than mine. Terms like RAID log, ceremony, and burndown come out unless the delivery genuinely cannot be described without them.
- Lead each bullet with the thing that shipped or the state that changed: a release, a migration, a cutover, a vendor onboarding, a policy rollout, a system retirement.
- Then name my part in it. Be exact about the line between what the team built and what I decided, sequenced, escalated, or negotiated. If a bullet reads as though I built the thing myself, fix it — the coordination is the part I can defend in an interview.
- Add scope only where my paste supports it: workstreams, teams or vendors coordinated, budget, duration, users or sites affected. Anything I have not given you becomes a bracketed placeholder such as [budget] or [teams coordinated].
Return the rewritten section, then a short list titled "Still missing" naming the scope figures that would strengthen each bullet and the one question I need to answer for each.
Rules — these override everything above:
- Use only the experience I give you. Do not invent employers, job titles, dates, degrees, certifications, skills, or metrics.
- If a number would strengthen a line and I have not given you one, write a placeholder like [X%] or [$X] for me to fill in. Do not estimate it.
- Do not add a tool, skill, or credential I did not list, however standard it is in my field.
- Rewrite, reorder, tighten and re-emphasize what is already there. Where I have given you too little to work with, ask me for it or leave [add detail].
Send this next
Ask it to name the bullet that still describes coordination rather than delivery, then rewrite that one after you supply the missing outcome.
Open inCopies the prompt, then opens the assistant
Pull scope and budget from your own project documents
You have a charter, status reports and a closeout deck, and none of it is on your resume. Use this to lift the real numbers out of your own documents instead of estimating them from memory
What to have ready
•A project charter, status report, closeout summary, or RAID log — remove anything confidential first
•Your own note on which parts you personally owned
•The dates the project ran
I am a project manager. I am going to paste project documents and I want the resume-relevant facts pulled out of them — not summarized, not embellished.
Documents:
[PASTE CHARTER, STATUS REPORT, CLOSEOUT SUMMARY, OR RAID LOG — REMOVE ANYTHING CONFIDENTIAL FIRST]
What I personally owned on this project:
[PASTE]
Dates it ran:
[PASTE]
Step 1. Build a table with one row per fact and these columns: the fact, its category (scope, budget, schedule, stakeholders, risk, outcome), and the exact line of my paste it came from. If it is not in my paste, it does not go in the table.
Step 2. Mark every row "mine", "shared", or "not mine" using what I told you I owned. Ask me about any row you cannot place.
Step 3. Using only the "mine" and "shared" rows, write 3 to 5 resume bullets, and show me which rows fed which bullet. Lead with what was delivered, then how big it was, how it tracked against plan, and who I had to align to get it done.
Step 4. List the gaps separately — the scope, budget, or schedule facts a reader would expect that my documents do not contain. Write each as a bracketed placeholder and a question, never as an estimate.
Where a document gives both a baseline and an actual — planned budget against final spend, planned date against delivery date — keep both, so the variance stays visible instead of collapsing into one round number.
Rules — these override everything above:
- Use only the experience I give you. Do not invent employers, job titles, dates, degrees, certifications, skills, or metrics.
- If a number would strengthen a line and I have not given you one, write a placeholder like [X%] or [$X] for me to fill in. Do not estimate it.
- Do not add a tool, skill, or credential I did not list, however standard it is in my field.
- Rewrite, reorder, tighten and re-emphasize what is already there. Where I have given you too little to work with, ask me for it or leave [add detail].
Send this next
Run it again on a second project, then ask which of the two belongs at the top of your resume for the role you are targeting.
Gemini: Paste the whole document into Gemini in one message rather than in excerpts, and keep to one project per conversation — the source-line column is only accurate when there is one document set to point at.
Open inCopies the prompt, then opens the assistant
Map your delivery record to a public-sector posting
Government and nonprofit postings tend to describe procurement, grant reporting and compliance milestones in their own vocabulary. Use this when your delivery record is a match and your wording is not
What to have ready
•The full job posting, including the responsibilities and qualifications sections
•Your current resume
•Funding, procurement, or reporting detail from your projects that is not on the resume yet
You are helping a project manager tailor an existing resume to one public-sector or nonprofit posting. You may reorder, reword, and re-emphasize anything that is already in my resume or my notes. You may not add experience that is in neither.
The posting:
[PASTE FULL POSTING]
My resume:
[PASTE]
Detail from my projects that is not on the resume yet — funding source, procurement route, reporting obligations, oversight bodies, compliance deadlines:
[PASTE OR WRITE "none"]
Work in four parts.
1. Requirement map. For each responsibility and qualification in the posting, mark it Met, Partly met, or Not met, and quote the line of my resume or notes that supports it. Every "Partly met" needs a sentence on what is missing.
2. Vocabulary translation. Where my resume describes the same work in commercial terms, put the posting's term beside mine — the posting may say solicitation, statement of work, subrecipient, period of performance, or steering committee where my resume says vendor selection, contract, partner, or project timeline. Translate only where the underlying work is genuinely the same. Where it is not the same, say so rather than stretching the word.
3. Rewrite. Give me the revised experience bullets, keeping every figure exactly as it appears in my paste, with the projects that map to the posting's core responsibilities first.
4. Honest gaps. List the Not met items plainly and tell me which are worth addressing in a cover letter and which are disqualifying. Do not invent adjacent experience to cover them.
Where the posting names a system, clearance, or certification I do not have, say it directly. I would rather know before I apply.
Rules — these override everything above:
- Use only the experience I give you. Do not invent employers, job titles, dates, degrees, certifications, skills, or metrics.
- If a number would strengthen a line and I have not given you one, write a placeholder like [X%] or [$X] for me to fill in. Do not estimate it.
- Do not add a tool, skill, or credential I did not list, however standard it is in my field.
- Rewrite, reorder, tighten and re-emphasize what is already there. Where I have given you too little to work with, ask me for it or leave [add detail].
Send this next
Ask it to draft the two cover-letter sentences that address your strongest "Partly met" item, using only what you supplied.
Open inCopies the prompt, then opens the assistant
General prompts that also work for a project manager resume
You have a gap of 6 months or more and want one factual line for it instead of an unexplained jump in dates
You are helping me write a single resume entry for a gap in my work history. The dates are [START MONTH YEAR] to [END MONTH YEAR]. Here is everything I actually did during that time, in my own words: [PASTE YOUR NOTES].
A chat window returns text. Paste it here and it opens in the editor, where 32 templates turn it into an interview-ready PDF. Free, no signup, and your draft stays in your browser.
