Use when planning high-stakes initiatives (migrations, launches, strategic changes) that require clear specifications, proactive risk identification (premortem/register), and measurable success criteria. Invoke when user mentions "plan this migration", "launch strategy", "implementation roadmap", "what could go wrong", "how do we measure success", or when high-impact decisions need comprehensive planning with risk mitigation and instrumentation.
View on GitHubskills/chain-spec-risk-metrics/SKILL.md
January 24, 2026
Select agents to install to:
npx add-skill https://github.com/lyndonkl/claude/blob/main/skills/chain-spec-risk-metrics/SKILL.md -a claude-code --skill chain-spec-risk-metricsInstallation paths:
.claude/skills/chain-spec-risk-metrics/# Chain Spec Risk Metrics ## Table of Contents - [Purpose](#purpose) - [When to Use This Skill](#when-to-use-this-skill) - [When NOT to Use This Skill](#when-not-to-use-this-skill) - [What Is It?](#what-is-it) - [Workflow](#workflow) - [Common Patterns](#common-patterns) - [Guardrails](#guardrails) - [Quick Reference](#quick-reference) ## Purpose This skill helps you create comprehensive plans for high-stakes initiatives by chaining together three critical components: clear specifications, proactive risk analysis, and measurable success metrics. It ensures initiatives are well-defined, risks are anticipated and mitigated, and progress can be objectively tracked. ## When to Use This Skill Use this skill when you need to: - **Plan complex implementations** - Migrations, infrastructure changes, system redesigns requiring detailed specs - **Launch new initiatives** - Products, features, programs that need risk assessment and success measurement - **Make high-stakes decisions** - Strategic choices where failure modes must be identified and monitored - **Coordinate cross-functional work** - Initiatives requiring clear specifications for alignment and risk transparency - **Request comprehensive planning** - User asks "plan this migration", "create implementation roadmap", "what could go wrong?" - **Establish accountability** - Need clear success criteria and risk owners for governance **Trigger phrases:** - "Plan this [migration/launch/implementation]" - "Create a roadmap for..." - "What could go wrong with..." - "How do we measure success for..." - "Write a spec that includes risks and metrics" - "Comprehensive plan with risk mitigation" ## When NOT to Use This Skill Skip this skill when: - **Quick decisions** - Low-stakes choices don't need full premortem treatment - **Specifications only** - If user just needs a spec without risk/metrics analysis (use one-pager-prd or adr-architecture instead) - **Risk analysis only** - If focused solely on identifying risks (