exec-narrative-patterns
Installation
SKILL.md
Exec Narrative Patterns
Different readers want different things. The same findings should not land the same way in a board deck, a CISO 1:1, and a regulator response.
Audience quick reference
| Audience | Length budget | Opening line wants | Technical depth | What they skip |
|---|---|---|---|---|
| Full board | 1 page max | Strategic posture one-liner | Low. No control IDs in body. | Operational detail, acronyms, tables with >5 rows |
| Audit committee | 2 pages | Risk-and-assurance posture | Medium. Control families OK, not IDs. | Strategy monologue, vendor names unless load-bearing |
| Risk committee | 2 pages | Residual risk movement | Medium-high. Framework names, risk scoring. | Program branding, tool selection detail |
| CEO weekly | Half page | What changed, what's blocking, what's asked | Low. Translate everything. | Framework politics, tool comparisons |
| CISO weekly | 1 page | What moved, what's blocked, what's next | High. Control IDs, tool names, owner names fine. | Over-explained context |
| Regulator / auditor | As long as needed | Precise scope + evidence | Maximum. IDs, artifact paths, timestamps. | Narrative softening |
Tone rules
Board and audit committee