When is this skill most useful?

It is most effective during the planning and design phases, especially when making critical architectural decisions that involve cost or security trade-offs.

What risk strategies does it support?

It evaluates risks based on four standard strategies: Avoidance, Mitigation, Transfer, and Acceptance, helping you choose the most appropriate path for your project constraints.

Does it generate documentation?

Yes, it can automatically draft Architecture Decision Records (ADRs) in the ./docs/adr directory to track technical choices and their justifications over time.

How does the Risk Assessment skill prevent errors?

It triggers a self-questioning loop that forces the AI to evaluate the 'why' behind an action, identifying flaws in logic or missing requirements before any code is written.

Can it help with complex debugging?

Absolutely. By applying the '5 Whys' analysis, it moves beyond surface-level symptoms to fix the underlying structural or logical flaws causing the bugs.

Autonomous Risk Assessment

Name: Autonomous Risk Assessment
Author: HikaruEgashira

byHikaruEgashira

Productivity & Workflow

Conducts autonomous risk assessments and root cause analysis during design phases to ensure robust architectural decisions.

About

This meta-skill empowers Claude to think critically before acting, preventing shallow implementations by applying structured frameworks like the '5 Whys' and assumption verification. It identifies potential technical and operational risks, suggests strategic mitigation plans (Avoid, Mitigate, Transfer, Accept), and automatically documents significant architectural decisions (ADRs) to maintain a transparent and future-proof project history. By forcing a self-questioning loop, it ensures that every code change or infrastructure update is justified, cost-effective, and aligned with the actual goals of the user.

Key Features

Root cause analysis using '5 Whys' to move beyond surface-level bug fixes
0 GitHub stars
Automated Architecture Decision Record (ADR) generation in a standardized format
Systematic risk identification with defined strategies (Avoid, Mitigate, Transfer, Accept)
Self-questioning framework to verify underlying assumptions and cost-effectiveness
Value-centric depth verification to ensure technical means match business ends

Use Cases

Performing deep debugging to identify architectural flaws causing recurring errors
Validating complex infrastructure requirements like VPC configurations before implementation
Documenting major technical shifts and trade-offs to prevent project knowledge rot

About

Key Features

Root cause analysis using '5 Whys' to move beyond surface-level bug fixes
0 GitHub stars
Automated Architecture Decision Record (ADR) generation in a standardized format
Systematic risk identification with defined strategies (Avoid, Mitigate, Transfer, Accept)
Self-questioning framework to verify underlying assumptions and cost-effectiveness
Value-centric depth verification to ensure technical means match business ends

Use Cases

Performing deep debugging to identify architectural flaws causing recurring errors
Validating complex infrastructure requirements like VPC configurations before implementation
Documenting major technical shifts and trade-offs to prevent project knowledge rot