stakeholder-risks-generator

Name: stakeholder-risks-generator
Availability: InStock
Author: KOHLEX

Aggregate risk signals from YAML, JSON logs, and architecture notes into a deduplicated RISKS.md register.

Updated Jun 4, 2026

Search Tags:#architecture #stakeholder #risk #risks #go/no-go #escalations #capabilities.yaml

Ready to run

npx skills add https://github.com/Kohlex/autopilot-plugin --skill stakeholder-risks-generator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: stakeholder-risks-generator
Source: https://github.com/Kohlex/autopilot-plugin/tree/main/skills/stakeholder-risks-generator
Command: npx skills add https://github.com/Kohlex/autopilot-plugin --skill stakeholder-risks-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

RISKS registers across products can be fragmented and hard to maintain. This Skill consolidates risk signals into a single, deduplicated, severity-sorted RISKS.md to support go/no-go decisions by stakeholders.

Core Features & Use Cases

Aggregate risk signals from capabilities.yaml (risk markers) + .autopilot-logs/escalations/*.json (L3 architecture conflicts) + ARCHITECTURE.md (out-of-scope notes) into one stable RISKS.md per product.
De-duplicate risks, score severity, and preserve stable risk_ids for continuity across regenerations.
Provide a consistent, stakeholder-facing risk register that supports governance reviews and decision-making.

Quick Start

Run the generator to produce the RISKS.md for a product by aggregating signals from capabilities.yaml, escalation logs, and ARCHITECTURE.md.

Frequently Asked Questions about stakeholder-risks-generator

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

FAQPage Schema

How do I consolidate fragmented product risk registers into a single file for stakeholder review?▼

To consolidate fragmented risk registers, this tool aggregates risk markers from capabilities.yaml, L3 escalation logs, and architecture notes into a single de-duplicated, severity-sorted RISKS.md file to support go/no-go decisions.

How does consolidating escalation logs and architecture notes into a risk register work?▼

Consolidating escalation logs works by reading .autopilot-logs/escalations/*.json and ARCHITECTURE.md, extracting BLOCKED-ARCH and out-of-scope notes, scoring severities, and preserving stable risk_ids across refreshes into a product-scoped RISKS.md.

Can I generate a stakeholder-facing risk register from capabilities.yaml for go/no-go decisions?▼

Yes, you can generate a stakeholder-facing risk register by reading risk markers like BLOCKED-EXT and DEFERRED directly from .planning/<product>/capabilities.yaml, scoring severities, and writing a governance-ready RISKS.md output.

What's the best way to maintain stable risk IDs across repeated risk register generations?▼

The best way to maintain stable risk IDs is using a generator that preserves stable risk_ids across refreshes, ensuring continuity by de-duplicating aggregated risk signals and writing them consistently into .planning/PRODUCT/RISKS.md.

Do I need ARCHITECTURE.md and capabilities.yaml files present to aggregate product risks?▼

Yes, you need ARCHITECTURE.md and .planning/<product>/capabilities.yaml files present, as the generator reads out-of-scope notes and risk markers from these specific inputs to produce the final consolidated risk register.

Why are my product risk signals scattered across multiple files instead of a unified register?▼

Risk signals are scattered because they originate across capabilities.yaml, escalation logs, and architecture notes; this tool resolves fragmentation by aggregating and de-duplicating these inputs into one severity-sorted RISKS.md.