Identify and classify project risks into a prioritized Markdown register.
npx skills add https://github.com/Binh230199/ai --skill risk-assessment-binh230199
Please help me install this Agent Skill. Skill: risk-assessment Source: https://github.com/Binh230199/ai/tree/main/.github/skills/risk-assessment Command: npx skills add https://github.com/Binh230199/ai --skill risk-assessment-binh230199
This Skill helps teams identify and manage project risks before they become schedule, technical, resource, external, or quality failures. It turns vague uncertainty into a concrete register with owners, severity levels, and action plans.
Analyze the attached project plan and produce a complete risk register with probability, impact, severity, mitigation, contingency, and review cadence.
High-intent search queries and answers about installing and using this skill.
To create a risk register, you analyze the project plan to classify risks across schedule, technical, resource, external, and quality categories, then score them by probability and impact. This process produces a Markdown register with derived severity, mitigation owners, and review cadence.
Identifying project risks involves using assumption inversion, pre-mortems, and dependency scanning to spot potential failures before they derail delivery. This approach transforms vague uncertainty into a concrete, prioritized risk register with actionable mitigation and contingency plans.
Writing mitigation and contingency plans involves scoring identified technical and resource risks by probability and impact to derive severity. You then assign specific mitigation owners and outline contingency actions to address these risks within the Markdown risk register.
Yes, you can use pre-mortems and assumption inversion during milestone reviews to actively scan dependencies and update your risk register. This allows you to adjust probability and impact scores, add new contingency actions, and set an ongoing review cadence.
Yes, this risk management approach applies directly to active issue response and plan updates by classifying emerging problems into the risk register. It calculates updated probability and impact scores, assigns mitigation owners, and defines contingency actions to resolve the active issue.
When building a risk register for schedule and quality failures, you should include schedule, technical, resource, external, and quality categories. Scoring risks in these categories by probability and impact ensures comprehensive coverage and produces a prioritized register with review cadence.
retz8Creates structured plans with goals, scope, milestones, owners, timelines, and dependencies for projects.
SSiertsemaMaintain a canonical risk register with IDs, scores, controls, and history.
matteocervelliAssess software vulnerabilities with CVSS scoring and remediation planning.
viktorbezdekAssess and mitigate project risks using structured registers and probability-impact matrices.
