pm-risk

Identify and assess project risks across technical, schedule, resource, and dependency dimensions.

3|Updated May 28, 2026

Search Tags:#planning #risk-management #mitigation #risk #project-management #stakeholders

Ready to run

npx skills add https://github.com/mahg-es/araya --skill pm-risk-mahg-es

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pm-risk
Source: https://github.com/mahg-es/araya/tree/main/skills/pm-risk
Command: npx skills add https://github.com/mahg-es/araya --skill pm-risk-mahg-es

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Risk management: identify, assess, and plan mitigations for project risks before they become blockers, ensuring smoother delivery.

Core Features & Use Cases

Surface risks across technical, schedule, resource, and dependency dimensions
Produce a centralized risk register at .araya/plan/spec/risk-register.md with owners, mitigations, and statuses
Enable sprint burn-down tracking and a risk matrix to guide corrective actions

Quick Start

Run a structured risk review at sprint start to identify, score, and assign mitigations.

Frequently Asked Questions about pm-risk

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

FAQPage Schema

How do I identify and assess project risks during sprint planning?▼

Project risks are identified and assessed during sprint planning by surfacing technical, schedule, resource, and dependency risks early to prevent blockers. A structured review scores likelihood and impact, assigning owners and mitigations to ensure smoother delivery.

What is a risk register and how does it help with risk mitigation?▼

A risk register is a centralized document tracking risk IDs, categories, likelihood, impact, mitigations, owners, and statuses. It outputs to a markdown file, providing a clear matrix to guide corrective actions and track sprint burn-down for ongoing risk mitigation.

Can I map dependency risks before they block my project delivery?▼

Dependency risks are mapped by applying risk assessment during dependency mapping and technology introductions. This process surfaces potential blockers across dependency dimensions early, allowing teams to plan mitigations and assign owners before delivery is impacted.

What's the best way to track project risk status across multiple sprints?▼

Tracking project risk status across sprints requires a centralized risk register combined with a risk matrix and sprint burn-down tracking. This approach monitors likelihood, impact, and mitigation status, guiding corrective actions throughout the project lifecycle.

Does this risk management approach work for technical and resource blockers?▼

Risk management applies across technical, schedule, resource, and dependency dimensions. It identifies and scores these specific blockers early, assigning mitigation owners to prevent them from impacting the overall project delivery timeline.