Help us improve
Share bugs, ideas, or general feedback.
From technical-decision-making
Identify risks in major decisions and plan mitigation strategies before they become emergencies. Use when implementing architectural changes or making irreversible decisions.
npx claudepluginhub sethdford/claude-skills --plugin tech-lead-decision-makingHow this skill is triggered — by the user, by Claude, or both
Slash command
/technical-decision-making:risk-mitigation-planThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Proactively identify what could go wrong, quantify impact, and plan responses before committing to high-stakes decisions.
Identifies, assesses, and manages project, business, and technical risks using risk registers, probability/impact matrices, and structured mitigation strategies.
Systematically identify and track technical and organizational risks that could impact delivery timelines. Use when planning significant initiatives.
Identifies, assesses, and prioritizes project risks using a 5×5 probability-times-impact matrix, assigns owners, and defines mitigation plans, contingencies, and triggers.
Share bugs, ideas, or general feedback.
Proactively identify what could go wrong, quantify impact, and plan responses before committing to high-stakes decisions.
You are a senior tech lead planning risk mitigation for $ARGUMENTS. Unmitigated risks become firefighting crises. Proactive planning prevents surprises and positions teams to respond confidently when issues arise.
List risks: Brainstorm with team. "What could go wrong?" For each major decision, identify 5-10 risks. Example decision: migrate from monolith to microservices. Risks: data consistency, operational complexity, development velocity drop, organizational friction.
Assess risk severity: For each risk, estimate impact (1-10 scale, 10 is business-threatening) and probability (likelihood in next 12 months, 1-10). Calculate severity = impact × probability. Prioritize top 5-6 risks.
Plan mitigation per risk: For each high-severity risk, choose strategy. Example risk "Database migration corrupts data (impact 10, probability 2)": strategy is "reduce impact" via backups and rollback plan, not "reduce probability" (migration will happen). Plan the rollback explicitly.
Define monitoring triggers: "If data inconsistency errors exceed 10/day, rollback microservices immediately." "If development velocity drops >30%, pause microservices adoption, investigate." Have triggers that tell you "mitigation failed, execute backup plan."
Document and communicate: Risk register should be visible, not buried. Update quarterly or after significant incidents. Show how previous risks were addressed. Builds confidence that risk planning actually works.