project failure risk forecaster
Stress-test project plans using a structured pre-mortem to identify and mitigate high-impact failure modes.
$5
Works with the AI tools you already use
Claude Code
Cursor
Codex CLI
GitHub Copilot
Gemini CLI+20 moreClaude CodeCursorCodex CLIGitHub CopilotGemini CLI
OpenClaw
Manus
Grok+17 agentsproject failure risk forecaster
Example session with this skill installed
Analyze the launch of our new API gateway scheduled for Q4. We have three teams involved, a hard deadline for a partner integration, and no dedicated QA team yet.
- Read your context and instructions
- Compiled the project failure risk
- Generated the document
I have completed a pre-mortem analysis for the API Gateway launch. The analysis assumes the project failed on December 31st due to integration delays and performance regressions.
Project Failure Risk Forecast: API Gateway Q4
Assumed Failure Statement
The API Gateway project failed on Dec 31st. The partner integration was missed, the gateway crashed under 50% load, and the lack of a QA team led to a critical auth bypass in production.
Fragile Assumptions Table
| Assumption | Severity | Confidence | Mitigation Needed |
|---|---|---|---|
| Dev teams can self-QA without delay | High | Low | Dedicated QA hire or external audit |
| Partner API spec is final | High | Med | Weekly syncs and versioned mocks |
| Throughput requirements are static | Med | High | Load testing in staging |
Ranked Failure Modes Table
| Rank | Failure Mode | Likelihood | Impact | Score |
|---|---|---|---|---|
| 1 | Partner integration delay due to spec changes | 4 | 5 | 20 |
| 2 | Production auth bypass due to lack of QA | 3 | 5 | 15 |
| 3 | Load-induced latency spikes at launch | 3 | 4 | 12 |
Sequencing Optimism Audit
| Task | Planned vs Realistic | Buffer Required |
|---|---|---|
| Auth Module Dev | 2 weeks / 4 weeks | 10 days (Security Review) |
| Partner Integration | 3 weeks / 6 weeks | 15 days (UAT) |
Controls Table
| Failure Mode | Early Warning | Preventative Action | Owner |
|---|---|---|---|
| QA Deficit | >5 open P1 bugs at week 6 | Outsource security audit now | CTO |
| Partner Lag | No response to ping in 48h | Create mock-server interface | Lead Dev |
Top Interventions
- Mock-Server Implementation: (Effort: Low / Benefit: High) Decouples dev from partner delays.
- External Security Audit: (Effort: Med / Benefit: Critical) Replaces missing QA for the most dangerous risk area.
Next steps
- Assign the Mock-Server task to the backend team today.
- Contact the security audit vendor for a Q4 slot.
- Review the buffer requirements with the Project Manager to adjust the partner launch date.
project-failure-risk-forecaster.pdf
PDF · document
Example file from a real run - the skill writes it into your workspace.
Connects securely to your tools. The creator never sees your data.
What you get
About this skill
The problem
Project plans often suffer from optimism bias and hidden dependencies that only surface after a failure occurs. Traditional risk registers are typically reactive and fail to identify the specific cascading effects that lead to total project collapse.
What it does
- Executes a structured pre-mortem by assuming project failure and working backward to find the cause.
- Maps hidden dependencies and identifies single points of failure in team burden or system architecture.
- Audits project sequencing to find buffer-less paths and unrealistic parallel task assumptions.
- Generates specific early-warning indicators and contingency plans for high-impact failure modes.
Why this beats prompting it yourself
This skill forces a specific cognitive shift from "how will this succeed" to "why did this fail," bypassing team defensiveness. It replaces vague risk lists with quantified scoring and actionable interventions, ensuring you focus resources on the risks that actually threaten delivery.
Use cases
- Pre-kickoff stress testing for high-stakes enterprise software deployments.
- Auditing aggressive release timelines when stakeholders demand simultaneous feature launches.
- Identifying bottlenecks in cross-functional projects with heavy third-party dependencies.
- Reviewing stalled projects to pivot before total resource exhaustion.
How to install
Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.
- 1
Download the ZIP
Free skills download straight away. Paid skills unlock right after purchase.
- 2
Unzip into your skills folder
Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.
- 3
Ask your agent to use it
Restart the agent if it was already running. It picks the skill up automatically - no config needed.
Skills folder by agent
Click the path to copy it. Create the folder if it does not exist yet.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
Fresh listing
Recently published to Agensi
30-day refund
Not a fit? Get your money back
Trust & safety
Security scanned
Verified clean 17 days ago
- Passed all security checks, Safe to install