AI Prompt Toolkit

Copy-ready prompts for better product delivery conversations

Use these prompts to get clearer thinking, faster diagnosis, and more useful next steps from AI. Choose your role, copy a prompt, customize the details, and use it in your preferred AI tool.

Built for Product Managers, Scrum Masters, and Development Managers.

Choose your role

Start with your role. Then copy, paste, and adapt.

Each prompt is designed around a real delivery challenge. Add your own team context, sprint data, product goals, or delivery constraints to make the response more specific.

Product Manager

Prompts for Product Managers

Use these prompts when you need help making sense of priorities, customer feedback, stakeholder pressure, or product trade-offs.

Turn competing requests into a clearer priority decision

Use this when stakeholders are asking for everything at once and you need a structured way to compare what matters most.

CONTEXT: I am managing a product area with several competing requests from stakeholders. Each request feels important, but the team does not have capacity to do everything in the next sprint or release.

TASK: Help me clarify which work should be prioritized first.

THINK THROUGH IT STEP BY STEP:
First, identify the key decision criteria I should use.
Then, create a simple prioritization framework.
Finally, explain how I should communicate the trade-offs to stakeholders.

OUTPUT: Prioritization recommendation + stakeholder talking points. Under 250 words.

Find patterns in messy customer feedback

Use this when you have notes from calls, surveys, tickets, or sales conversations and want to identify the strongest product themes.

CONTEXT: I have a collection of customer feedback from recent calls, support tickets, and sales conversations. The feedback is messy and includes feature requests, complaints, and general comments.

TASK: Help me identify the most important product themes.

THINK THROUGH IT STEP BY STEP:
First, group the feedback into themes.
Then, identify which themes suggest real customer pain versus individual preferences.
Finally, recommend which themes deserve deeper discovery.

OUTPUT: Theme summary + recommended next discovery questions. Under 300 words.

Prepare a clear trade-off explanation

Use this when you need to explain why the team should say no, delay something, or choose one direction over another.

CONTEXT: We need to choose between improving an existing workflow and building a new feature requested by a major stakeholder. Both options have value, but we cannot do both right now.

TASK: Help me explain the trade-off clearly.

THINK THROUGH IT STEP BY STEP:
First, compare the short-term and long-term impact of each option.
Then, identify the risks of choosing each path.
Finally, write a concise recommendation I can share with stakeholders.

OUTPUT: Trade-off summary + recommendation. Under 250 words.

Scrum Master

Prompts for Scrum Masters

Use these prompts to make team patterns more visible, improve retrospectives, and identify where delivery flow is breaking down.

Move beyond generic retro answers

Use this when retrospectives are getting repetitive and the team is not surfacing useful actions.

CONTEXT: Our team retrospectives have started to feel repetitive. We often discuss the same issues, but the actions are vague and do not lead to visible improvement.

TASK: Help me design a better retrospective conversation.

THINK THROUGH IT STEP BY STEP:
First, identify why the current retrospective may not be producing change.
Then, suggest 5 stronger retro questions.
Finally, propose a simple way to turn the discussion into measurable follow-up actions.

OUTPUT: Retro structure + action format. Under 300 words.

Identify what is slowing the team down

Use this when work is moving, but not smoothly — too much waiting, rework, handoff, or context switching.

CONTEXT: Our team is completing work, but delivery feels slower than it should. Stories often wait for review, get blocked by dependencies, or require rework late in the sprint.

TASK: Help me diagnose the biggest flow problems.

THINK THROUGH IT STEP BY STEP:
First, identify the likely sources of delay.
Then, suggest what data or observations I should check.
Finally, recommend 3 experiments the team could try next sprint.

OUTPUT: Flow diagnosis + 3 improvement experiments. Under 300 words.

Reduce sprint overcommitment

Use this when the team regularly starts more work than it finishes and needs a healthier planning conversation.

CONTEXT: Our team regularly commits to more work than it finishes. The team is working hard, but sprint goals are often missed and unfinished work rolls over.

TASK: Help me facilitate a better sprint planning conversation.

THINK THROUGH IT STEP BY STEP:
First, identify the patterns that lead to overcommitment.
Then, suggest questions I can ask during planning.
Finally, recommend how to create a more realistic sprint goal.

OUTPUT: Planning facilitation guide + sample questions. Under 300 words.

Development Manager

Prompts for Development Managers

Use these prompts to understand capacity, diagnose bottlenecks, and make better decisions across teams, systems, and delivery commitments.

Understand whether workload is uneven — or something deeper

Use this when one squad seems underloaded while others are consistently overloaded.

CONTEXT: I manage 3 squads on a shared platform. Squad A is consistently finishing early while Squads B and C are overloaded. I suspect the work allocation process is the problem, not the people.

TASK: Help me diagnose whether this is a workload distribution issue or something deeper.

THINK THROUGH IT STEP BY STEP:
First, identify the most likely structural causes of uneven workload across squads.
Then, suggest 3 diagnostic questions I should investigate using our sprint data.
Finally, propose 2 rebalancing approaches with trade-offs.

OUTPUT: Diagnosis framework + 2 options. Under 250 words.

Find the technical constraints slowing delivery

Use this when delivery is being blocked by architecture, environments, dependencies, code quality, or review bottlenecks.

CONTEXT: Several teams are reporting slower delivery because of technical dependencies, review delays, and recurring production issues. It is unclear whether the main bottleneck is architecture, process, or team capacity.

TASK: Help me identify the most likely technical bottlenecks.

THINK THROUGH IT STEP BY STEP:
First, list the common technical constraints that slow delivery across teams.
Then, suggest what evidence I should look for in our delivery and incident data.
Finally, recommend 3 actions I could take as a development manager.

OUTPUT: Bottleneck diagnosis + recommended actions. Under 300 words.

Spot delivery risk before it becomes a missed commitment

Use this when a project is still “on track” publicly, but you suspect risk is building underneath.

CONTEXT: A cross-team initiative is currently marked as on track, but there are signs of risk: unclear ownership, unresolved dependencies, and several items moving late in the sprint.

TASK: Help me assess the real delivery risk.

THINK THROUGH IT STEP BY STEP:
First, identify the warning signs that this initiative may be at risk.
Then, suggest questions I should ask team leads.
Finally, create a short risk summary I can share with leadership.

OUTPUT: Risk assessment + leadership update. Under 250 words.

The CTO Framework

Context — Brief the AI like you’d brief a new team member.

Task — What do you need done? Be specific.

Output — What should the result look like? How long? What format?

Want to go deeper? Add reasoning steps: “First analyze X, then consider Y, finally recommend Z.”

Product Manager

Prompts for Product Managers

Use these prompts when you need help making sense of priorities, customer feedback, stakeholder pressure, or product trade-offs.

Turn competing requests into a clearer priority decision

Use this when stakeholders are asking for everything at once and you need a structured way to compare what matters most.

CONTEXT: I am managing a product area with several competing requests from stakeholders. Each request feels important, but the team does not have capacity to do everything in the next sprint or release.

TASK: Help me clarify which work should be prioritized first.

THINK THROUGH IT STEP BY STEP:First, identify the key decision criteria I should use.Then, create a simple prioritization framework.

Finally, explain how I should communicate the trade-offs to stakeholders.

OUTPUT: Prioritization recommendation + stakeholder talking points. Under 250 words.

Copy prompt

Find patterns in messy customer feedback

Use this when you have notes from calls, surveys, tickets, or sales conversations and want to identify the strongest product themes.

CONTEXT: I have a collection of customer feedback from recent calls, support tickets, and sales conversations. The feedback is messy and includes feature requests, complaints, and general comments.

TASK: Help me identify the most important product themes.

THINK THROUGH IT STEP BY STEP:First, group the feedback into themes.Then, identify which themes suggest real customer pain versus individual preferences.

Finally, recommend which themes deserve deeper discovery.

OUTPUT: Theme summary + recommended next discovery questions. Under 300 words.

Copy prompt

Prepare a clear trade-off explanation

Use this when you need to explain why the team should say no, delay something, or choose one direction over another.

CONTEXT: We need to choose between improving an existing workflow and building a new feature requested by a major stakeholder. Both options have value, but we cannot do both right now.

TASK: Help me explain the trade-off clearly.

THINK THROUGH IT STEP BY STEP:First, compare the short-term and long-term impact of each option.Then, identify the risks of choosing each path.

Finally, write a concise recommendation I can share with stakeholders.

OUTPUT: Trade-off summary + recommendation. Under 250 words.

Copy prompt

Scrum Master

Prompts for Scrum Masters

Use these prompts to make team patterns more visible, improve retrospectives, and identify where delivery flow is breaking down.

Move beyond generic retro answers

Use this when retrospectives are getting repetitive and the team is not surfacing useful actions.

CONTEXT: Our team retrospectives have started to feel repetitive. We often discuss the same issues, but the actions are vague and do not lead to visible improvement.

TASK: Help me design a better retrospective conversation.

THINK THROUGH IT STEP BY STEP:First, identify why the current retrospective may not be producing change.Then, suggest 5 stronger retro questions.

Finally, propose a simple way to turn the discussion into measurable follow-up actions.

OUTPUT: Retro structure + action format. Under 300 words.

Copy prompt

Identify what is slowing the team down

Use this when work is moving, but not smoothly — too much waiting, rework, handoff, or context switching.

CONTEXT: Our team is completing work, but delivery feels slower than it should. Stories often wait for review, get blocked by dependencies, or require rework late in the sprint.

TASK: Help me diagnose the biggest flow problems.

THINK THROUGH IT STEP BY STEP:First, identify the likely sources of delay.Then, suggest what data or observations I should check.

Finally, recommend 3 experiments the team could try next sprint.

OUTPUT: Flow diagnosis + 3 improvement experiments. Under 300 words.

Copy prompt

Reduce sprint overcommitment

Use this when the team regularly starts more work than it finishes and needs a healthier planning conversation.

CONTEXT: Our team regularly commits to more work than it finishes. The team is working hard, but sprint goals are often missed and unfinished work rolls over.

TASK: Help me facilitate a better sprint planning conversation.

THINK THROUGH IT STEP BY STEP:First, identify the patterns that lead to overcommitment.Then, suggest questions I can ask during planning.

Finally, recommend how to create a more realistic sprint goal.

OUTPUT: Planning facilitation guide + sample questions. Under 300 words.

Copy prompt

Development Manager

Prompts for Development Managers

Use these prompts to understand capacity, diagnose bottlenecks, and make better decisions across teams, systems, and delivery commitments.

Understand whether workload is uneven — or something deeper

Use this when one squad seems underloaded while others are consistently overloaded.

CONTEXT: I manage 3 squads on a shared platform. Squad A is consistently finishing early while Squads B and C are overloaded. I suspect the work allocation process is the problem, not the people.

TASK: Help me diagnose whether this is a workload distribution issue or something deeper.

THINK THROUGH IT STEP BY STEP:First, identify the most likely structural causes of uneven workload across squads.Then, suggest 3 diagnostic questions I should investigate using our sprint data.

Finally, propose 2 rebalancing approaches with trade-offs.

OUTPUT: Diagnosis framework + 2 options. Under 250 words.

Copy prompt

Find the technical constraints slowing delivery

Use this when delivery is being blocked by architecture, environments, dependencies, code quality, or review bottlenecks.

CONTEXT: Several teams are reporting slower delivery because of technical dependencies, review delays, and recurring production issues. It is unclear whether the main bottleneck is architecture, process, or team capacity.

TASK: Help me identify the most likely technical bottlenecks.

THINK THROUGH IT STEP BY STEP:First, list the common technical constraints that slow delivery across teams.Then, suggest what evidence I should look for in our delivery and incident data.

Finally, recommend 3 actions I could take as a development manager.

OUTPUT: Bottleneck diagnosis + recommended actions. Under 300 words.

Copy prompt

Spot delivery risk before it becomes a missed commitment

Use this when a project is still “on track” publicly, but you suspect risk is building underneath.

CONTEXT: A cross-team initiative is currently marked as on track, but there are signs of risk: unclear ownership, unresolved dependencies, and several items moving late in the sprint.

TASK: Help me assess the real delivery risk.

THINK THROUGH IT STEP BY STEP:First, identify the warning signs that this initiative may be at risk.Then, suggest questions I should ask team leads.

Finally, create a short risk summary I can share with leadership.

OUTPUT: Risk assessment + leadership update. Under 250 words.

Copy prompt

The CTO Framework

Context — Brief the AI like you’d brief a new team member.

Task — What do you need done? Be specific.

Output — What should the result look like? How long? What format?

Want to go deeper? Add reasoning steps: “First analyze X, then consider Y, finally recommend Z.”

Join our Newsletter

Join our newsletter for practical insights on product delivery, organizational agility, and AI-enabled ways of working.

Start with your role. Then copy, paste, and adapt.

Prompts for Product Managers

Turn competing requests into a clearer priority decision

Find patterns in messy customer feedback

Prepare a clear trade-off explanation

Want more practical delivery tools like this?

Prompts for Scrum Masters

Move beyond generic retro answers

Identify what is slowing the team down

Reduce sprint overcommitment

Want more practical delivery tools like this?

Prompts for Development Managers

Understand whether workload is uneven — or something deeper

Find the technical constraints slowing delivery

Spot delivery risk before it becomes a missed commitment

Want more practical delivery tools like this?

The CTO Framework

Prompts for Product Managers

Turn competing requests into a clearer priority decision

Find patterns in messy customer feedback

Prepare a clear trade-off explanation

Prompts for Scrum Masters

Move beyond generic retro answers

Identify what is slowing the team down

Reduce sprint overcommitment

Prompts for Development Managers

Understand whether workload is uneven — or something deeper

Find the technical constraints slowing delivery

Spot delivery risk before it becomes a missed commitment

The CTO Framework

Join our Newsletter