30
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill lyndonkl/claude --skill chain-spec-risk-metrics- SKILL.md8.9 KB
Overview
This skill helps you plan high-stakes initiatives by combining a clear specification, a proactive premortem-style risk register, and measurable success metrics. It produces an actionable artifact that aligns stakeholders, anticipates failure modes, and defines how you will measure progress and validate success. Use it to turn vague goals into accountable plans with owners and instrumentation.
How this skill works
The skill gathers initiative context (goals, constraints, stakeholders, baseline) and writes a detailed specification covering scope, approach, requirements, dependencies, and timeline. It runs a premortem to surface failure causes, converts those into a prioritized risk register with mitigations and owners, and defines leading/lagging/counter metrics with baselines, targets, and tracking cadence. Finally, it validates completeness against a rubric and delivers a cohesive plan.
When to use it
- Planning complex implementations (migrations, system redesigns)
- Launching new products, features, or programs that need risk and measurement
- Making high-impact strategic decisions where failure modes must be anticipated
- Coordinating cross-functional initiatives that need shared specs and accountability
- Requesting a comprehensive roadmap: “plan this migration”, “what could go wrong”, or “how do we measure success”
Best practices
- Collect context up front: goals, constraints, stakeholders, baselines
- Be specific and measurable in specs and metrics (quantify targets and timelines)
- Run a structured premortem then convert findings into a prioritized risk register
- Assign an owner to every risk and metric and define monitoring cadence
- Include counter-metrics to protect quality, security, and team health
- Treat the plan as living: update risks and metrics after milestones and incidents
Example use cases
- Migrate a monolith to microservices with phased rollouts, mitigations for data consistency, and deployment/latency metrics
- Launch a new payment gateway with risk register for compliance and fraud, plus adoption and error-rate metrics
- Implement a major infrastructure upgrade with rollback criteria, load-test requirements, and MTTR targets
- Design a company-wide process change with organizational risks, training plan, and user adoption KPIs
FAQ
Provide initiative goal, timeline, constraints (budget/resources), stakeholders, current baseline metrics, and whether this is migration/greenfield/enhancement.
How are risks prioritized?
Risks are rated by likelihood and impact, converted to a priority score, then mitigated by feasibility and cost; each risk receives an owner and status.