tech-leader-exec-briefing

Writes jargon-free executive briefings that translate technology topics into business impact, cost, and risk.

Updated Jan 28, 2026
One-click install
npx skills add https://github.com/scanady/nexus-skills --skill tech-leader-exec-briefing-scanady
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-leader-exec-briefing
Source: https://github.com/scanady/nexus-skills/tree/main/skills/tech-leader-exec-briefing
Command: npx skills add https://github.com/scanady/nexus-skills --skill tech-leader-exec-briefing-scanady

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Technology leaders struggle to communicate technical issues to CEOs, CFOs, COOs, and boards in language that drives decisions. This Skill reframes technology topics as business narratives — covering stakes, cost, risk, and recommendations — so executives can act without decoding jargon. ## Core Features & Use Cases - Guided Story Discovery: A structured interview phase sharpens vague topics into a clear narrative with stakes, urgency, and a point of view before drafting begins. - Audience-Tuned Drafting: Adjusts tone and emphasis for CEO, CFO, COO, board, or full leadership team, with a translation table mapping technical realities to executive concerns. - Structured Output Formats: Uses a reference template with Summary, Context, Business Implications, Options, Recommendation, and Decision Required sections, plus one-pager and expanded variants. - Use Case: A CIO needs to brief the CFO on a data platform migration that is four months behind with a vendor renewal in six weeks; the Skill produces a decision-ready briefing quantifying the $2M exposure and recommending a path. ## Quick Start Ask the agent to write an executive briefing for the CFO explaining the business risk and cost of the delayed data platform migration, with a clear recommendation.

Frequently Asked Questions about tech-leader-exec-briefing

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

FAQPage Schema
How do I write an executive briefing about a technology topic?▼

Start by clarifying the triggering event, business stakes, and your recommendation, then draft using a structure of Summary, Context, Business Implications, Recommendation, and Decision Required. This Skill guides that discovery with targeted questions before drafting.

How to explain technical debt or system risk to a CEO or board?▼

Translate the technical reality into business terms: technical debt becomes operational drag and delivery speed, security vulnerabilities become regulatory exposure and reputational risk. Lead with the business objective, never the architecture.

Can the briefing format change for different executives?▼

Yes. Tone adjusts by audience: strategic and forward-looking for CEOs, financially grounded for CFOs, execution-focused for COOs, and governance-framed for boards. Short one-pager and expanded variants with a supporting detail appendix are also supported.

What if my briefing topic is still vague or undeveloped?▼

The Skill runs a guided discovery phase, asking one question at a time (maximum five to seven) to surface the triggering event, stakes, and your point of view. It confirms the narrative arc with you before drafting anything.

When should I not use a written executive briefing?▼

Avoid it for purely technical audiences who need implementation detail, or for fast-moving incidents requiring real-time verbal alignment. The format targets decision-ready written communication for senior business leaders, typically 400 to 800 words.