silent-risk-accumulator

Detect and map interacting delivery risks from exceptions, gaps, and deferred decisions into an evidence-linked combination map.

Updated Jun 1, 2026
One-click install
npx skills add https://github.com/aurora-atoms/lattice --skill silent-risk-accumulator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: silent-risk-accumulator
Source: https://github.com/aurora-atoms/lattice/tree/main/skills/silent-risk-accumulator
Command: npx skills add https://github.com/aurora-atoms/lattice --skill silent-risk-accumulator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies how individually tolerable exceptions, skipped tests, and deferred decisions combine into material delivery exposure before they trigger a major failure.

Core Features & Use Cases

  • Interaction Mapping: Visualizes how disparate risks amplify one another across a delivery case.
  • Leverage Ranking: Identifies the smallest set of pressure-relief actions that reduce the most material exposure.
  • Use Case: Use this during a project gate review to determine if a combination of minor technical debt and expired assumptions requires immediate mitigation or can be safely accepted as residual risk.

Quick Start

Use the silent-risk-accumulator skill to analyze the current delivery case for interacting risks and recommend the highest-leverage pressure-relief actions.

Frequently Asked Questions about silent-risk-accumulator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify interacting delivery risks before they cause a major project failure?

To identify interacting delivery risks, you analyze structured delivery evidence like exceptions, test gaps, and deferred decisions to map how individually tolerable risks combine into material exposure. This reveals cumulative vulnerabilities before they trigger failures.

What is a silent risk accumulator in project governance and risk management?

A silent risk accumulator is a mechanism where minor technical debt, skipped tests, and expired assumptions interact and amplify one another. In project governance, it represents the cumulative exposure from individually tolerable exceptions that remain hidden until reviewed.

How do I find high-leverage mitigation paths for combined technical debt and deferred decisions?

Finding high-leverage mitigation paths involves mapping risk interactions to rank pressure-relief actions. By analyzing architectural drift and delivery evidence, you identify the smallest set of actions that reduces the most material delivery exposure.

Can I use delivery evidence and risk records to determine if technical debt requires immediate mitigation?

Yes, you can use structured delivery evidence and risk records during a project gate review to evaluate combined exposure. This determines whether accumulated technical debt and deferred decisions require immediate mitigation or can be safely accepted as residual risk.

What input is needed to map interacting risks across a bounded delivery case?

Mapping interacting risks requires structured input of delivery evidence, risk records, and architectural drift. This bounded delivery case data is necessary to generate an evidence-linked risk-combination map that visualizes cumulative exposure.