Running a project without AI is like navigating without GPS — you'll get there eventually, but you'll waste time on wrong turns. These prompts help you plan sprints, break down complex deliverables, and spot risks before they derail your timeline. Tested across ChatGPT, Gemini, and Claude so you pick the right model for each PM challenge.
| What you're trying to do | הכי טוב ל |
|---|---|
| Plan a two-week sprint | Claude |
| Break large tasks into subtasks | ChatGPT |
| Identify and mitigate project risks | Claude |
| Map and manage stakeholders | Gemini |
| Write clear project status reports | ChatGPT |
| Facilitate effective retrospectives | Gemini |
פרומפטים
Plan a two-week sprint
I need to plan a sprint for my team. Project: [project name and goal] Team members: [list roles and availability] Backlog items: [list 10-15 user stories or tasks with estimates] Sprint length: [1 week / 2 weeks] Previous sprint velocity: [story points completed if known] Create: 1. A prioritized sprint backlog with story point assignments 2. Task breakdown for the top 5 items (subtasks with time estimates) 3. Dependencies between tasks and the critical path 4. Risk flags — items likely to spill over and why 5. Daily standup focus areas for each day of the sprint 6. Sprint goal statement in one sentence
הכי טוב ל: CLAUDE
Claude excels at identifying hidden dependencies between tasks and provides realistic velocity estimates. It won't overstuff your sprint just because you asked for more.
Tested Feb 15, 2026
טיפים מקצועיים
Include your team's actual velocity from the last 3 sprints, not the ideal one. AI plans much better sprints when it knows how much your team actually delivers vs. how much you wish they did.
Break large tasks into subtasks
I have a large task that needs to be broken down: Task: [describe the big deliverable] Deadline: [when it's due] Team members available: [who can work on this] Technical constraints: [tools, platforms, dependencies] Definition of done: [what 'complete' looks like] Break this into: 1. A work breakdown structure with 3 levels of detail 2. Estimated hours for each subtask 3. Which subtasks can run in parallel vs. must be sequential 4. The minimum viable version that could ship in half the time 5. Acceptance criteria for each subtask 6. A Gantt-style timeline showing the critical path
הכי טוב ל: CHATGPT
ChatGPT produces the most detailed and actionable work breakdown structures. Its subtask granularity is perfect for tools like Jira or Asana — not too broad, not too micro.
Tested Feb 15, 2026
טיפים מקצועיים
Ask for the 'minimum viable version' every time. It forces the AI to identify what's truly essential vs. nice-to-have, which is the hardest part of project scoping.
Identify and mitigate project risks
Analyze the risks for this project: Project: [name and description] Timeline: [start and end dates] Team: [size and experience level] Budget: [total budget] External dependencies: [vendors, APIs, approvals needed] Stakeholders: [who cares about this project] Provide: 1. A risk register with 8-10 risks ranked by likelihood and impact 2. For each risk: trigger condition, impact description, and mitigation plan 3. The top 3 risks that could kill the project entirely 4. Early warning indicators for each critical risk 5. A contingency plan for the single most likely risk 6. A risk review cadence recommendation
הכי טוב ל: CLAUDE
Claude identifies non-obvious risks that other models miss — especially people risks and organizational politics. It also provides the most realistic impact assessments instead of generic severity ratings.
Tested Feb 15, 2026
טיפים מקצועיים
Include what went wrong on your last similar project. AI catches patterns across projects and will flag risks you've already experienced but might not think to mention.
Map and manage stakeholders
Help me manage stakeholders for this project: Project: [name and one-sentence summary] Stakeholders: [list each person with their role, department, and interest in the project] Project phase: [kickoff / in-progress / nearing launch] Biggest political challenge: [what makes this project politically tricky] Create: 1. A stakeholder map: power vs. interest grid with each person placed 2. Communication plan: what each stakeholder needs to know, how often, and in what format 3. A RACI matrix for key project decisions 4. Scripts for managing a stakeholder who wants to expand scope 5. An escalation framework: when and how to escalate issues 6. A 'pre-mortem' — what stakeholder-related failure looks like and how to prevent it
הכי טוב ל: GEMINI
Gemini creates the most structured and visually clear RACI matrices and communication plans. Its stakeholder maps are immediately presentable to leadership without reformatting.
Tested Feb 15, 2026
טיפים מקצועיים
Be honest about the political dynamics in your prompt. AI can only help you navigate stakeholder politics if it knows who has informal power, who's resistant, and who's championing the project.
Write clear project status reports
Generate a project status report from these details: Project: [name] Reporting period: [this week / this month] Milestones completed: [list what shipped] Milestones in progress: [list what's being worked on] Blockers: [anything stuck and why] Budget status: [on track / over / under] Team morale: [any concerns] Write: 1. An executive summary (3 sentences: overall status, biggest win, biggest concern) 2. A red/yellow/green status for: scope, timeline, budget, quality, team 3. Key accomplishments with business impact 4. Risks and blockers with owner and resolution plan 5. Next week's priorities 6. One decision needed from leadership (with recommendation)
הכי טוב ל: CHATGPT
ChatGPT writes the most polished executive-ready status reports. It leads with impact rather than activity, which is what leadership actually wants to read.
Tested Feb 15, 2026
טיפים מקצועיים
Always include one decision you need from leadership. Status reports that only inform get ignored; reports that require action get read. Make it easy for them to say yes or no.
Facilitate effective retrospectives
Help me run a retrospective for my team: Project/sprint: [what just finished] Team size: [number of people] What went well: [list 3-5 wins] What didn't go well: [list 3-5 problems] Previous retro action items: [what was decided last time] Team dynamic: [any tension or morale issues] Design a retro that includes: 1. A creative format beyond 'start/stop/continue' (with facilitation instructions) 2. 5 targeted questions to surface the real issues 3. A prioritization method for deciding which problems to fix 4. Action items template: specific, owned, and time-bound 5. A follow-up plan to ensure action items actually happen 6. A 'team health' pulse check with 5 dimensions to rate
הכי טוב ל: GEMINI
Gemini designs the most creative retro formats with clear facilitation steps. Its action item templates are specific enough that accountability is built in, not an afterthought.
Tested Feb 15, 2026
טיפים מקצועיים
Share what happened with LAST retro's action items before running a new one. If previous items weren't completed, the team needs to address that pattern before generating more commitments.
Based on actual testing — not assumptions. See our methodology
Gemini
Best for structured project artifacts like RACI matrices, stakeholder maps, and retro formats. Produces clean, presentation-ready outputs that work in Google Workspace immediately.
Results from Gemini 2.0 Flash · Tested Feb 15, 2026ChatGPT
Best for status reports and work breakdown structures. Writes executive-ready summaries and creates task breakdowns at the right granularity for PM tools like Jira and Asana.
Results from GPT-4o · Tested Feb 15, 2026Claude
Best for risk analysis and sprint planning. Identifies hidden dependencies and non-obvious risks, especially people and political dynamics. Gives honest assessments instead of optimistic projections.
Results from Claude 3.5 Sonnet · Tested Feb 15, 2026Grok
Cuts through project management bureaucracy to identify what actually matters for delivery. Strong at calling out scope creep and unnecessary process, but less diplomatic in stakeholder communication advice than Claude.
Results from Grok 2 · Tested Feb 15, 2026Plan for 70% capacity, not 100%. Teams that plan sprints at full capacity always miss targets. Buffer 30% for meetings, context switching, and surprise requests. AI will try to fill every hour — tell it your real available time.
Write the 'definition of done' before starting any task. Scope creep happens when 'done' isn't defined upfront. Ask AI to write acceptance criteria for every major deliverable before work begins.
Track decisions, not just tasks. Most project delays come from unmade decisions, not incomplete work. Ask AI to create a decision log alongside your task board.