pre-mortem-analyst

What This Skill Does

The Pre-Mortem Analyst is a sophisticated cognitive framework tool designed to bypass human optimism bias during the planning phase of any project. Unlike standard risk assessment—which asks team members what might possibly go wrong—the pre-mortem technique mandates the assumption that the project has already suffered a catastrophic failure. By shifting the perspective to a future where failure is a certainty, the agent liberates stakeholders to voice hidden doubts, systemic vulnerabilities, and uncomfortable realities that would otherwise be suppressed by groupthink.

This skill systematically guides users through a structured analytical process: setting the scene, brainstorming diverse failure vectors across people, process, technology, and external domains, ranking these risks by impact and likelihood, and culminating in actionable mitigation strategies. It acts as an impartial auditor for your strategic plans.

Installation

You can integrate this skill into your OpenClaw environment by executing the following command in your terminal: clawhub install openclaw/skills/skills/artyomx33/pre-mortem-analyst

Use Cases

• Strategic Planning: Validate the feasibility of a product launch or new market entry.
• Complex Engineering: Assess the durability of system architecture before code deployment.
• Organizational Change: Identify potential cultural or operational friction points during internal restructuring.
• Critical Decision Making: Provide a 'stress test' for any high-stakes initiative where failure would be costly.

Example Prompts

1. "We are planning to launch our new CRM system in three months. Can you run a pre-mortem on this project?"
2. "Imagine this failed six months down the line. What would kill this marketing campaign?"
3. "I'm worried about our current project velocity. Can we do a quick risk analysis using the pre-mortem framework to see what might go wrong?"

Tips & Limitations

• Encourage Radical Candor: The output quality is directly proportional to the inputs provided. Do not censor failure scenarios; even improbable ones provide value.
• Use Sparingly: This tool is best used at major decision gates rather than daily tasks, as it is cognitively heavy.
• Monitor Continuously: The 'Warning Signs' generated by the tool should be integrated into your project dashboards as early-warning KPIs.
• Limitation: This is a diagnostic tool, not an executor. It identifies failure modes but requires human action to implement the mitigation strategies.