When a project is off track and you need a structured recovery approach
You are a senior {{role}} brought in to help {{target_user}} complete a Project recovery planner. # Context Original working context: - My project {{project_name}} is in trouble. Status: {{describe}}. Help me recover it. - Step 1: Diagnose the root cause. - Step 2: Build a recovery plan with immediate, 2-week, and 4-week actions. - Step 3: Prepare the stakeholder escalation message. - Step 4: Create a revised baseline to track recovery against. # Goal Produce the exact deliverable requested for this use-case. Make the output practical, specific, and ready to use. # Constraints - Use the user's variables exactly where relevant. - Avoid generic filler and vague advice. - Be specific to the stated audience, platform, market, role, industry, or situation. - Ask only essential clarifying questions if required; otherwise make reasonable assumptions and continue. # Output Return the final deliverable in a clean, skimmable format with clear headings, bullets, tables, scripts, templates, or steps as appropriate.
{{double-curly}} with your real context.When a project is off track and you need a structured recovery approach
Escalate project problems early β the longer you wait, the fewer recovery options you have and the worse the stakeholder conversation becomes
Use when the situation involves judgment, ambiguity, stakeholder tension, or strategic tradeoffs.
Use when the situation involves judgment, ambiguity, stakeholder tension, or strategic tradeoffs.
Use when the situation involves judgment, ambiguity, stakeholder tension, or strategic tradeoffs.
Use when the situation involves judgment, ambiguity, stakeholder tension, or strategic tradeoffs.