premortem

Identifies project risks and blind spots from a structured pre-implementation analysis.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/jey3dayo/apm-workspace --skill premortem-jey3dayo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: premortem
Source: https://github.com/jey3dayo/apm-workspace/tree/main/catalog/skills/premortem
Command: npx skills add https://github.com/jey3dayo/apm-workspace --skill premortem-jey3dayo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps identify potential risks and blind spots in project planning, requirements, design, estimation, and task decomposition before implementation begins.

Core Features & Use Cases

  • Failure Prediction: Analyze project context and identify potential risks.
  • Blind Spot Discovery: uncover overlooked issues in planning, design, and estimation.
  • Use Case: Before starting development on a new feature, use this Skill to analyze the project's context, ask key questions, and receive a report with prioritized risks and next actions.

Quick Start

Run the premortem skill with the repository 'project-repo'.

Frequently Asked Questions about premortem

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify potential risks in project planning before implementation?

You can discover blind spots in task decomposition by running a structured premortem analysis on your repository context. This approach analyzes project context to uncover overlooked issues in planning, design, and estimation, generating a report with prioritized risks and next actions.

Do I need repository access to perform failure prediction on a new feature?

Yes, you need repository access to perform failure prediction because the analysis requires parsing project context to generate relevant questions and identify high-impact risks tailored to your specific project type and size.

When do I need to run a premortem analysis for my software development project?

You need to run a premortem analysis before starting development on a new feature or implementation phase. It helps analyze the project's context, ask key questions, and receive a report with prioritized risks and next actions to guide proactive planning.

What is the best way to uncover blind spots in requirements and estimation?

The best way to uncover blind spots in requirements and estimation is using a structured premortem analysis approach that examines repository context to identify overlooked issues. This generates prioritized risk reports and next actions to guide proactive planning.

Can a premortem analysis handle various project types and sizes for risk identification?

Yes, a premortem analysis can handle various project types and sizes for risk identification. The structured approach emphasizes identifying high-impact risks and guiding proactive planning across different project scales and contexts.