program-portfolio-composition

Synthesize findings from multiple framework plugins into a single portfolio view.

1|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/rifh2000/claude-grc-engineering. --skill program-portfolio-composition-rifh2000
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: program-portfolio-composition
Source: https://github.com/rifh2000/claude-grc-engineering./tree/main/plugins/grc-reporter/skills/program-portfolio-composition
Command: npx skills add https://github.com/rifh2000/claude-grc-engineering. --skill program-portfolio-composition-rifh2000

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consolidates results from multiple frameworks into a single readable portfolio instead of listing the controls from each framework.

Core Features & Use Cases

  • Coverage table (one row per framework) summarizes framework alignment and deltas.
  • Leverage list identifies cross-framework patterns that appear across multiple frameworks.
  • Watch list flags at-risk items and escalations across the portfolio.

What the appendix carries

  • Per-framework full gap reports linked
  • SCF-to-framework crosswalks and mappings
  • Connector inventory and coverage map

Quick Start

Use program-portfolio-composition to generate a consolidated portfolio view from active framework findings.

Frequently Asked Questions about program-portfolio-composition

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

FAQPage Schema
How do I consolidate multiple GRC framework findings into a single portfolio report?

Consolidating multiple GRC framework findings into a single portfolio report requires synthesizing controls from 3 to 8 frameworks into a compact, vendor-agnostic view. This collapses detailed controls into SCF patterns and expands them as needed for readability.

What is the best way to report cross-framework alignment without listing every control?

Reporting cross-framework alignment without listing every control involves generating a coverage table that summarizes framework alignment and deltas. This provides one row per framework to present a concise portfolio view instead of exhaustive control lists.

How does a portfolio view identify cross-framework patterns and at-risk findings?

A portfolio view identifies cross-framework patterns and at-risk findings by utilizing a leverage list to flag patterns appearing across multiple frameworks, and a watch list to escalate at-risk items across the entire portfolio.

Can I summarize findings if I am reporting across fewer than 3 or more than 8 frameworks?

Summarizing findings is designed specifically for reporting across 3 to 8 frameworks. Operating outside this range is not recommended as the collapsing and expanding logic is optimized to avoid showing every framework control in full within this specific boundary.

What should be included in the appendix of a framework portfolio composition?

The appendix of a framework portfolio composition should include per-framework full gap reports, SCF-to-framework crosswalks and mappings, and a connector inventory with a coverage map to validate consistency and provide detailed backend documentation.

Why does my portfolio report need to collapse framework controls into SCF patterns?

Collapsing framework controls into SCF patterns avoids overwhelming reporting with full control listings. This mechanism validates consistency and readability by providing a compact presentation that expands detailed framework mappings only when needed.