grc-reporter

Plugin grc-reporter from marketplace grc-engineering-suite in GRCEngClub/claude-grc-engineering. Commands read from the repo's manifest — today.

Skills (5)

• automation-coverage-analysis

  Composes week-over-week automation coverage narratives. Use when /report:automation-coverage is running. Frames the delta for leadership around time saved, quality of evidence, and forward-looking compounding value.

• context-bootstrap

  Setup guidance for users running a /report:* command before their toolkit has enough context. Use when a report command detects missing findings, frameworks, or history. Walks the user through installation and first collection rather than generating a hollow report.

• exec-narrative-patterns

  Audience-specific tone and format guidance for leadership communications. Use when drafting any /report:* output to tune length, framing, and technical depth to the reader (board, audit committee, CEO, weekly CISO, regulator).

• program-portfolio-composition

  Patterns for synthesizing findings across multiple frameworks into one readable portfolio view. Use when a /report:* command is pulling from more than one framework plugin and needs to avoid drowning the reader in control IDs.

• so-what-translation

  Translates GRC findings, risks, and program activity into language leadership actually reads. Use when any /report:* command is composing output intended for a CISO, CIO, or above. Opinionated rules on what lands and what doesn't.

Slash commands (4)

• /grc-reporter:automation-coverage

  Week-over-week automation coverage analysis with ROI narrative

• /grc-reporter:board-brief

  Quarterly audit-committee or board-ready narrative from findings, incidents, and residual risk

• /grc-reporter:exec-summary

  Weekly 1-page executive summary for the CISO and direct leadership

• /grc-reporter:program-health

  Portfolio view across every framework in scope, sized for CISO 1:1s and program reviews