Route latent delivery risks to specialized diagnostic capabilities for preventive actions.
npx skills add https://github.com/aurora-atoms/lattice --skill risk-ahead
Please help me install this Agent Skill. Skill: risk-ahead Source: https://github.com/aurora-atoms/lattice/tree/main/skills/risk-ahead Command: npx skills add https://github.com/aurora-atoms/lattice --skill risk-ahead
This Skill addresses the challenge of hidden dependencies and silent risks in complex delivery projects by routing them to the smallest sufficient specialist before they become blocking issues.
Invoke the risk-ahead skill by providing a bounded delivery case, current stage, and relevant evidence to receive a routing decision and a preventive action plan.
High-intent search queries and answers about installing and using this skill.
To identify hidden dependencies and silent risks in delivery projects, you can route bounded delivery cases and project evidence to specialized diagnostic capabilities. This categorizes exposures into domains like shadow dependencies and compliance gaps to produce actionable preventive artifacts.
The best way to route compliance preflight and rework warnings is to analyze project stage and gate status evidence. This routing mechanism categorizes latent delivery exposures into five specific domains, directing each to the smallest sufficient specialist for targeted resolution.
Automate risk management routing for ambiguous project delays by inputting structured project stage, gate status, and evidence. The system evaluates the bounded delivery case to determine if the delay stems from a shadow dependency or a compliance gap.
Yes, you need structured input of project stage, gate status, and evidence to use latent delivery risk routing. The system requires this bounded delivery case data to accurately categorize silent risks and generate a specific preventive action plan.
Specialist routing for governance risks distinguishes itself by linking every identified exposure to concrete evidence and generating a specific preventive artifact. It routes silent risks to the smallest sufficient specialist rather than applying a generalized mitigation strategy.
You should not use automated dependency mapping when you lack bounded delivery cases, structured project stage data, or concrete evidence. Without these required inputs, the routing mechanism cannot accurately categorize latent risks or produce preventive artifacts.
aurora-atomsGenerate structured, versioned playbooks from feature delivery case evidence.
jabrenaAssess Java enterprise systems against NIS2 cybersecurity risk management requirements.
aurora-atomsDetect convergence gaps in requirement, decision, and implementation history.
cyberswatIdentify fatal flaws, dependencies, and hidden assumptions in evaluate output.
