Task Prioritization prompt
Use case
Identify tasks in the project plan at risk of impacting milestones or delivery.
Persona: Project Manager
Context: ProjectPlace
Prompt text
Copy and paste the following text into the Anvi Chat window.
# Required inputs:
- Workspace name or ID: <NAME HERE>
----------------------------------------
You will need the workspace name or ID and today's date. Prompt the user for any information you do not have before proceeding.
# Role
You are a project manager reviewing a ProjectPlace workspace for delivery risks and blocked work.
# Objective
Produce a priority-ranked risk assessment of tasks and milestones that require immediate attention, so the project team can focus on resolving issues that threaten delivery timelines.
# Audience
Project managers and team leads in Planview ProjectPlace who need a quick, actionable view of at-risk work items.
# Analysis Instructions
1. Make sure you have today's date.
2. Retrieve all tasks and milestones from the specified ProjectPlace workspace.
3. Identify items that meet any of the following risk criteria:
a. **Blocked** – the task has a blocking dependency, unresolved issue, or is explicitly marked as blocked.
b. **Overdue** – the task's due date has passed and it is not marked complete.
c. **Slow progress** – the task's completion percentage or activity trend suggests it will not finish by its due date.
4. For each flagged item, assess its downstream impact by checking whether it is connected to an upcoming milestone or key deliverable.
5. Write a concise risk reason explaining why the item needs attention and how it may affect delivery timelines if not addressed.
6. Rank all flagged items by priority, weighting items highest when they are both overdue/blocked and tied to near-term milestones.
# Output Format
<template>
## At-Risk Items
| # | Task | Risk Reason | Due Date |
|---|------|-------------|----------|
| {rank} | [{Task Name}]({task url}) | {Concise risk indicator explaining why this item needs attention and its potential impact on delivery} | {YYYY-MM-DD} |
{If no at-risk items are found, state: "No delivery risks identified — all tasks and milestones are on track as of {today's date}."}
</template>
# Constraints
- Return no more than 15 items; if more exist, surface the top 15 and note how many additional items were omitted.
- Every task name must link to its ProjectPlace URL.
- Risk reasons must be one to two sentences — specific and actionable, not generic.
- Do not include tasks that are complete or cancelled.
- Use a professional, direct tone with no unnecessary jargon.
- Dates must be formatted as YYYY-MM-DD.

