risk-analysis

Name: risk-analysis
Availability: InStock
Author: petrsimonidesxart

Identify and structure product, delivery, and systemic risks into prioritized reports.

Updated Mar 8, 2026

Search Tags:#planning #qa #risk-management #risk-analysis #risk-reporting #epics-stories

Ready to run

npx skills add https://github.com/petrSimonidesXart/xPmGateway --skill risk-analysis-petrsimonidesxart

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: risk-analysis
Source: https://github.com/petrSimonidesXart/xPmGateway/tree/main/.gaai/core/skills/cross/risk-analysis
Command: npx skills add https://github.com/petrSimonidesXart/xPmGateway --skill risk-analysis-petrsimonidesxart

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically identify, structure, and prioritize risks across product, delivery, and systemic domains before they derail plans.

Core Features & Use Cases

Structured risk identification across product, delivery, and systemic areas.
Severity ranking and mitigation guidance based on impact and likelihood.
Generates risk reports to contexts/artefacts/risk-reports/{story_id}.risk-report.md with an anti-collision guard to prevent overwrites.

Use cases include pre-epic/story finalization, pre-execution planning, following QA failures, or after major scope changes.

Quick Start

Provide artefacts and memory context, then run the risk analysis to generate a risk report.

Frequently Asked Questions about risk-analysis

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

FAQPage Schema

How do I identify and prioritize product risks before finalizing epics and stories?▼

To identify product risks early, systematically structure and rank them across product, delivery, and systemic domains by impact and likelihood before finalizing epics and stories. This generates prioritized risk reports with mitigation guidance.

When do I need to perform a delivery risk analysis during project planning?▼

You need delivery risk analysis during pre-execution planning, following QA failures, or after major scope changes. Analyzing risks at these planning phases prevents delivery failures by structuring severity rankings and mitigation strategies before issues derail plans.

Can I use risk reporting to prevent overwriting existing analysis files?▼

Yes, risk reporting includes an anti-collision guard to prevent overwrites. Generating risk reports to specific artefact paths ensures existing risk analysis files remain protected while structuring newly identified systemic and delivery risks.

What's the best way to structure systemic risks after a major scope change?▼

The best way to structure systemic risks after major scope changes is reading existing artefacts and memory context, then analyzing risks across systemic domains. This generates structured risk reports with severity rankings and mitigation guidance.

How do I generate a risk report for QA iterations without losing previous data?▼

Generate risk reports for QA iterations by reading artefacts and memory, then writing new reports with an anti-collision guard. This prevents overwriting previous risk analysis data while structuring newly identified product and delivery risks.

Does risk analysis require specific dependencies or external components to function?▼

No, risk analysis requires no external dependencies or components to function. It systematically identifies and structures risks by reading provided artefacts and memory context, then generating prioritized risk reports independently.