arn-spark-stress-premortem

Automate post-launch failure analysis using Gary Klein's pre-mortem methodology.

31|3|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/AppsVortex/arness --skill arn-spark-stress-premortem
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: arn-spark-stress-premortem
Source: https://github.com/AppsVortex/arness/tree/main/plugins/arn-spark/skills/arn-spark-stress-premortem
Command: npx skills add https://github.com/AppsVortex/arness --skill arn-spark-stress-premortem

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps teams analyze product concepts after launch by conducting a structured pre-mortem to uncover why a launch failed and to surface actionable mitigation.

Core Features & Use Cases

  • Reads the product concept, pillars, competitive landscape, and target personas to drive a rigorous 3-root-cause analysis across core experience, trust/security, and audience dimensions.
  • Uses the pre-mortem protocol and report template to generate a comprehensive premortem report with a risk-priority matrix.
  • Writes the final report to the project's stress-tests/premortem-report.md, overwriting previous reports on reruns.

Quick Start

Invoke the skill on a current product concept to generate a premortem report and save it to the stress-tests directory.

Frequently Asked Questions about arn-spark-stress-premortem

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

FAQPage Schema
What is a premortem analysis for product concepts?

A premortem analysis anticipates product launch failures by assuming failure and working backward to uncover root causes. This skill automates Gary Klein's methodology to surface actionable mitigation across trust, audience, and core experience dimensions.

How do I run a premortem stress test on my product concept?

To run a premortem stress test, invoke the skill on your product concept. It reads your pillars, competitive landscape, and target personas, then generates a report with a risk-priority matrix saved to your stress-tests directory.

Can I use this premortem skill without defining target personas and competitive landscape?

This skill requires a fully defined product concept including target personas, competitive landscape, and pillars to drive its rigorous three-root-cause analysis and generate an accurate risk assessment.

Does running a premortem report overwrite existing stress test files?

Yes, running a premortem report overwrites existing reports on reruns. The skill writes the final report to the project's stress-tests/premortem-report.md file, replacing previous versions to maintain a single current analysis.

What is the difference between a premortem and a standard risk assessment?

A premortem uses an adversarial approach assuming a launch already failed to proactively surface forensic root causes. A standard risk assessment lists potential issues, while this premortem generates a risk-priority matrix based on simulated post-launch failure.