skills.rest
bketelsen
bketelsenCOMMUNITY
Explore all skills by this author →
Website𝕏@bketelsenGitHub

risk-analysis

Identify, classify, and prioritize product, delivery, and systemic risks from project documentation.

1|Updated Mar 12, 2026
Search Tags:#quality assurance#project planning#risk management#systemic risks#delivery risks#product risks
One-click install
npx skills add https://github.com/bketelsen/truenas-mcp --skill risk-analysis-bketelsen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: risk-analysis
Source: https://github.com/bketelsen/truenas-mcp/tree/main/.gaai/core/skills/cross/risk-analysis
Command: npx skills add https://github.com/bketelsen/truenas-mcp --skill risk-analysis-bketelsen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill systematically identifies, structures, and prioritizes risks before they escalate into failures, ensuring more predictable project outcomes.

Core Features & Use Cases

  • Risk Identification: Scans project artifacts (PRDs, Epics, Stories) and memory context to find potential risks.
  • Risk Classification & Prioritization: Categorizes risks (product, delivery, systemic), assesses impact and likelihood, and ranks them by severity.
  • Use Case: Before finalizing a new feature's user stories, activate this skill to uncover potential ambiguities, technical feasibility issues, or missing validations that could derail development.

Quick Start

Activate the risk-analysis skill to identify and structure risks for the provided Epic documentation.

Frequently Asked Questions about risk-analysis

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

FAQPage Schema
How do I identify product and delivery risks before finalizing user stories?▼

Risk management assesses project artifacts and memory contexts to classify and prioritize threats by impact and likelihood. It derives severity scores to systematically identify systemic, delivery, and product risks before they escalate into failures.

What's the best way to classify and prioritize systemic risks in project documentation?▼

Classifying systemic risks involves categorizing identified threats into product, delivery, or systemic groups, then assessing their impact and likelihood. This structured assessment derives a severity ranking to prioritize mitigation efforts effectively.

Can I analyze risks using filesystem-based artifacts and memory bundles?▼

Yes, risk analysis operates directly on filesystem-based artifacts alongside optional memory bundles. It processes these project documentation contexts to systematically identify and structure potential threats without requiring external integrations.

Does project planning risk management work with epics and PRDs?▼

Yes, risk management specifically scans epics, PRDs, and user stories during project planning. It evaluates these documentation artifacts to proactively identify technical feasibility issues and missing validations that could derail development.

What limitations should I expect when deriving severity from impact and likelihood assessments?▼

Deriving severity depends entirely on the completeness of your filesystem artifacts and memory contexts. If project documentation lacks detail or omits edge cases, the structured risk report may miss ambiguities and fail to capture all systemic threats.

Related Skills

Explore More Product & Management Skills→
Ocean326Ocean326

product-manager

Create PRDs, FRs, NFRs, epics, and user stories from a project brief.

Community
Advanced
Fr-e-dFr-e-d
157

risk-analysis

Identify, classify, and prioritize product, delivery, and systemic risks in project artefacts.

Community
Intermediate
agol586agol586

speckit-analyze

Analyze project specification, planning, and task documents for consistency and quality.

Community
Intermediate
AcidicSoilAcidicSoil
1

risk-profile

Score implementation risks with Probability × Impact and generate mitigations and test priorities.

Community
Advanced