risk-docs

Creates a rated risk register with mitigations by scanning project documentation and interviewing the user.

Updated May 24, 2026
One-click install
npx skills add https://github.com/pirras-torres/pirras-marketplace --skill risk-docs-pirras-torres
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: risk-docs
Source: https://github.com/pirras-torres/pirras-marketplace/tree/main/plugins/pi-dev/skills/risk-docs
Command: npx skills add https://github.com/pirras-torres/pirras-marketplace --skill risk-docs-pirras-torres

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Software projects accumulate hidden risks across architecture decisions, domain complexity, and sprint blockers, but teams rarely consolidate them into a single rated register. This Skill scans existing project docs to surface risk candidates automatically, then guides a structured interview to confirm, rate, and document each risk with mitigation plans. ## Core Features & Use Cases - Automatic Risk Discovery: Reads backend/frontend architecture, domain model, PRD, personas, and sprint discovery docs to derive risk candidates with sources. - Structured Rating: Scores each risk by probability and impact (Critical/High/Medium/Low/Negligible) using a defined matrix. - Mitigation Planning: Captures mitigation plans and activation triggers for every Critical and High risk, writing the result to docs/06_decisions/risk_docs.md. - Use Case: Before sprint planning, run the Skill to turn open architecture decisions and pending discovery items into a rated risk register the team can review. ## Quick Start Ask the assistant to create a risk register for the project by scanning the existing docs and interviewing you about probability, impact, and mitigations.

Frequently Asked Questions about risk-docs

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

FAQPage Schema
How do I create a risk register for a software project?▼

Run the risk-docs Skill, which scans your existing docs for risk candidates, asks you to confirm and add risks, then rates each by probability and impact. It writes the result to docs/06_decisions/risk_docs.md with mitigation plans for Critical and High risks.

How are risks scored in the risk register?▼

Each risk is rated on probability (High/Medium/Low) and impact (High/Medium/Low). The combination maps to a score: H×H is Critical, H×M or M×H is High, M×M is Medium, and L×L is Negligible.

What documents does the risk scan read?▼

It reads backend and frontend architecture docs, the domain model, sprint discovery files, the PRD, and personas. Open decisions, complex invariants, pending items, and churn triggers are extracted as risk candidates with their source noted.

Do low-priority risks need mitigation plans?▼

No. Only Critical and High risks require a mitigation plan and an activation trigger. Low and Medium risks are documented in a summary table, and "Accept" is a valid mitigation for Low risks.

What if my project has no docs folder yet?▼

The Skill searches for a docs folder up to three levels deep, asks which to use if multiple exist, and creates docs/ if none is found. Without existing docs, risk candidates come entirely from the interview questions.