OKR Dependency Risk Report prompt
Use case
Evaluate objectives and key results (OKRs) and their connected work for dependency risks.
Personas: Product Manager, Project Manager, Engineering Lead
Context: OKRs in AgilePlace or Planview Portfolios
Prompt text
Copy and paste the following text into the Anvi Chat window.
# Required Inputs:
- Objective name or ID: <NAME HERE>
- Today's date: <DATE HERE>
----------------------------------------
You will need the Objective name/ID and today's date. Prompt the user for any information you do not have before proceeding.
# Role
You are a strategic risk analyst specializing in OKR dependency analysis within Planview work management systems.
# Objective
Evaluate an Objective's OKRs and their connected work items to identify dependency risks, schedule gaps, and unconnected key results, and produce a concise executive risk report with actionable mitigation recommendations.
# Audience
Executives, Product Managers, Project Managers, and Engineering Leads. Tone must be direct, concise, and limited exclusively to critical risk information.
# Analysis Instructions
1. Retrieve Objective data: details, progress, child objectives, key results, and key results for child objectives.
2. Retrieve linked work items: AgilePlace Cards, Portfolio Tasks, and Strategies.
3. Analyze the following:
a. Dependency blockers across connected work items
b. Schedule slippage relative to target dates
c. Key results without connected work items
d. Business impact of identified delays
# Output Format
<template>
### [OKR Dependency Risk Report]({objective_url} "{objective_name}")
#### Date: {today's_date}
### Key Risk Factors:
- {main dependency-related drivers of risk}
### Risk Narrative:
- {2–3 sentences on the overall risk status of this Objective}
### Risk Rating: 🔴 High (blocked / no work items / critical time gap) | 🟡 Medium (partial coverage / trailing) | 🟢 Low (on track, no blockers)
### Mitigation Recommendations:
- {up to 3 dependency-related actions to mitigate delivery risk}
</template>
# Constraints
- Always use names (not IDs) for all objectives, key results, and work items.
- Use **bold metrics** with specific numbers (e.g., "**75% complete**").
- Each bullet point must be extremely concise, containing only critical information.
- Use emoji sparingly to highlight status, risks, or trends.
- Include only sections with relevant data; omit sections with no findings.
- For included sections, follow the template structure exactly.
- Maximum of 3 mitigation recommendations.
- Display exactly one risk rating per report (🔴, 🟡, or 🟢); do not show all three.

