risk-assessment

Identify and document delivery risks into a prioritized risk register with mitigations.

1|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/yknothing/prodcraft --skill risk-assessment-yknothing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: risk-assessment
Source: https://github.com/yknothing/prodcraft/tree/main/skills/03-planning/risk-assessment
Command: npx skills add https://github.com/yknothing/prodcraft --skill risk-assessment-yknothing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Risk assessment identifies what could derail the plan and what the team will do about it. In Prodcraft, this is not generic project management paperwork. It is the technical and delivery-focused pass that protects sequencing, scope, and release confidence, especially when work crosses service boundaries, migrations, or external dependencies.

Core Features & Use Cases

  • Identify risk categories across architecture, dependency, migration, operational, and security aspects.
  • Score material risks with likelihood, impact, earliest detection, mitigations, and owners to inform planning.
  • Convert risks into actionable planning steps: resequencing tasks, spikes, contingencies, or added observability.
  • Produce a live risk register to support sprint planning and release decisions.
  • Use case: evaluate a feature's migration impact and external dependencies to adjust roadmap and quality gates.

Quick Start

Provide a risk assessment for a planned release by capturing the top risks with owners and mitigations.

Frequently Asked Questions about risk-assessment

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

FAQPage Schema
How do I identify delivery risks for cross-domain work and external dependencies?

Identify delivery risks by evaluating architecture, dependency, migration, operational, and security categories, scoring material risks by likelihood and impact to produce a prioritized risk register with mitigations.

What's the best way to document migration risks before they derail a planned release?

Document migration risks by capturing the top risks with owners and mitigations, converting them into actionable planning steps like resequencing tasks, spikes, contingencies, or added observability to protect release confidence.

Can I use a risk register to adjust roadmap sequencing and quality gates?

Yes, a live risk register supports sprint planning and release decisions by scoring material risks with earliest detection and owners, allowing you to adjust roadmap sequencing and align with project quality gates.

How do I convert identified architecture and dependency risks into actionable planning steps?

Convert risks into actionable planning steps by scoring them on likelihood and impact, then resequencing tasks, adding spikes, defining contingencies, or adding observability to mitigate schedule surprises.

When do I need a technical risk assessment for project planning?

You need a technical risk assessment during planning for cross-domain work, migrations, and external dependencies to identify what could derail the plan and define what the team will do about it.

What inputs are required to generate a prioritized risk register with mitigations?

Generating a prioritized risk register requires inputs like a task-list, dependency-graph, and architecture-doc to evaluate risk categories and produce mitigations aligned with the project quality gate.