Identify, assess, and plan mitigations for project risks systematically.
/risk-register-builder3-4 hrs → 30 min
Compared to doing it manually
/risk-register-builderType this in Claude to run the skill
Risks are invisible until they explode. Projects fail from known unknowns that nobody tracked. Post-mortems reveal risks that were obvious in hindsight.
/welcome/risk-register-builder in Claude to run the skill/strategic-roadmap-reviewA facilitated thinking exercise: look back at what happened, then look forward to set strategic direction — before building the tactical roadmap.
/prioritization-engineScore and rank features using RICE, ICE, or weighted scoring with clear documentation.
/north-star-finderIdentify and validate your product's North Star metric with supporting input metrics.
/go-to-market-strategyCreates a complete GTM plan with channels, messaging, timeline, and success metrics
A risk register is a document that tracks potential risks to a project or product. It includes: risk description, likelihood, impact, mitigation strategies, owners, and status. It's a living document updated throughout the project.
Use a risk matrix: plot likelihood (x-axis) vs impact (y-axis). High likelihood + high impact risks need immediate mitigation. Low likelihood + low impact can be accepted. Focus attention on the top-right quadrant.
A risk is something that might happen. An issue is something that has happened. Risk registers track potential problems; issue logs track actual problems. Risks become issues when they materialize.
Get all 70 skills running in a system that knows your company, product, and customers.
All 70 skills + your company context in one system.