OKR Dependency Risk Report prompt

Evaluate OKRs and their connected work for dependency risks. 
You’ll need the name or ID of the objective to analyze and today’s date; prompt the user for any info you don’t have.    
 
1. Retrieve Objective data (details, progress, child objectives, key results, and key results for child objectives) 
 
2. Retrieve linked work items (AgilePlace Cards, Portfolios Tasks & Strategies) 
 
3. Analyze: dependency blockers, schedule slippage, key results without connected work, business impact of delays. 
 
This is for an executive audience so ensure your response is clear and limited to ONLY critical information.  
 
Format your analysis using the template below: 
- ALWAYS USE names (not IDs) for all objectives, key results, work items. 
- Use **bold metrics** with specific numbers (e.g., "**75% complete**"). 
- Ensure each bullet point is EXTREMELY concise, containing ONLY critical information. 
- Use emoji sparingly to highlight status, risks, or trends. 
- Include only sections with relevant data. For those included, follow the template structure exactly. 
 
<template> 
### [OKR Dependency Risk Report](link to objective_url with objective name as text) 
#### Date: [Today’s date] 
 
### Key Risk Factors: 
- Main dependency-related drivers of risk 
 
### Risk Narrative: 
- 2-3 sentences on the 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>