Revue des risques avec MCP : détecter les tâches en retard et les blocages cachés
Identify project risks by detecting overdue tasks, tasks with many comments but no progress, and tasks lacking owners using MCP. This workflow shows you how to surface hidden blockers, propose mitigations, and generate escalation messages.
Ce que ce workflow permet
Risk review with MCP proactively identifies project risks:
Résultats clés
- Overdue detection: Find tasks that are past their due dates
- Stale task identification: Surface tasks with activity but no progress
- Ownership gaps: Identify tasks without clear owners
- Mitigation proposals: Get AI-suggested actions to address risks
- Escalation support: Generate messages for escalating critical risks
Prérequis
Before using this workflow, ensure you have:
- Corcava MCP server configured in your AI assistant
- API key with read access to tasks and comments
- Tasks with due dates and assignees set
- Tasks with comment history
Workflow pas à pas
Step 1: Find Overdue Tasks
Start by identifying tasks that are past their due dates:
Overdue Tasks Prompt
What the AI does:
- Calls
list_taskswithdue_date: "overdue" - Filters out completed tasks
- Calculates days overdue
- Groups by project and assignee
Step 2: Detect Stale Tasks
Identify tasks with activity but no progress:
Stale Task Detection Prompt
What the AI does:
- Calls
list_tasksto get active tasks - Calls
list_task_commentsfor each task - Analyzes comment count vs. status change date
- Identifies tasks with activity but no progress
Step 3: Find Unassigned Tasks
Surface tasks without clear ownership:
Unassigned Task Detection Prompt
What the AI does:
- Calls
list_tasksto get all tasks - Filters tasks with null or empty assignee
- Groups by project
- Highlights unassigned tasks
Step 4: Propose Mitigations
Get AI-suggested actions to address each risk:
Mitigation Proposal Prompt
What the AI does:
- Analyzes each risk type
- Considers task context (project, assignee, due date)
- Proposes specific mitigation actions
- Prioritizes risks and mitigations
Step 5: Generate Escalation Messages
Create messages for escalating critical risks:
Escalation Message Prompt
What the AI does:
- Identifies high-priority risks
- Drafts escalation messages
- Tailors messages for different audiences
- Includes task context and links
Complete Workflow Prompts
Here are complete, copy-paste ready prompts:
Full Risk Review
Use this when: You want a complete risk assessment
Quick Risk Check
Use this when: You want a quick risk overview
Project-Specific Risk Review
Use this when: You want to focus on a specific project
Workflow Variants
Variant 1: Blocker-Focused Review
Focus specifically on blocked tasks:
What happens: AI focuses on blocked tasks and unblocking strategies
Variant 2: Timeline Risk Analysis
Analyze risks to project timelines:
What happens: AI analyzes risks specifically related to project timelines
Example: Complete Risk Review Session
Here's a real example of how a risk review session flows:
User Prompt
AI Response (Risk Review)
Risk Review - March 20, 2026
Overdue Tasks (3 found):
- API Documentation - Due: Mar 15 (5 days overdue) - Project: API Redesign - Assignee: John
Mitigation: Check with John on status, consider extending deadline or reassigning - Homepage Mockups - Due: Mar 18 (2 days overdue) - Project: Q2 Marketing - Assignee: Sarah
Mitigation: Follow up with Sarah, check if client feedback is blocking progress
Stale Tasks (2 found):
- Database Migration - 8 comments, last status change: Mar 5 (15 days ago) - Project: Backend - Assignee: Mike
Mitigation: Schedule a check-in with Mike, review comments to understand blockers
Unassigned Tasks (1 found):
- Content Calendar Review - Project: Q2 Marketing - Due: Mar 25
Mitigation: Assign to appropriate team member or mark as blocked until owner identified
High-Priority Escalation:
"API Documentation task is 5 days overdue and may be blocking other work. Recommend immediate follow-up with John to assess status and determine if deadline extension or reassignment is needed."
Troubleshooting
Too Many Risks Found
Symptom: Risk review shows too many issues
Possible causes:
- Filters are too broad
- Many tasks are actually at risk
Fix: Narrow scope: "Find only high-priority risks" or "Focus on tasks due in next 2 weeks"
Mitigations Too Generic
Symptom: Proposed mitigations are vague
Possible causes:
- AI lacks context about tasks
- Task descriptions are too brief
Fix: Ask for specific actions: "Propose concrete, actionable mitigations with owners and timelines"
Related Tools
This workflow uses these Corcava MCP tools:
list_tasks
Find overdue, stale, and unassigned tasks
list_task_comments
Analyze comment activity for stale task detection
get_task
Get task details for risk analysis
Related Use Cases
Weekly Status Report
Generate status reports with risk sections
Client Progress Report
Include risk highlights in client updates
Dependency Tracking
Identify dependency-related risks
Proactively Identify Project Risks
Connect your AI assistant to Corcava and detect risks before they become problems