exec-vs-working-deck
Stop presenting the working deck to executives — the two-deck split (answer-first exec cut vs. exploration-rich working deck), the compression rules from 40 slides to 8, and the appendix strategy that keeps the depth one click away. Use when asked turn this analysis into an exec version, my leadership readout went badly, how do I compress 40 slides to 10 minutes, or what do execs actually want in a deck. Produces the exec cut with the answer-first order, the compression map (what survived, where the rest went), and the Q&A appendix plan.
npx skills add mohitagw15856/pm-claude-skills --skill exec-vs-working-deck --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Exec Vs Working Deck Skill The working deck — forty slides of exploration, methodology, and dead ends — is a *diary of the analysis*. Presenting it to executives narrates the journey chronologically, landing the answer at slide 34 of a meeting that ended attention-wise at slide 6. The exec cut inverts the geometry: the answer first (slide 2 at the latest), the three pieces of evidence that carry it, the risks and the ask — 6–10 slides — with the working deck demoted to appendix, where it does its real executive job: *existing*, as the visible proof of rigor behind every Q&A answer ("slide 24 has that cohort — here"). ## What This Skill Produces - **The exec cut** — answer-first, 6–10 slides, built from the working deck's strongest material - **The compression map** — every working-deck section: promoted / compressed to a line / appendixed / cut - **The appendix strategy** — the Q&A-ordered depth, indexed so retrieval is instant in the room - **The two-deck discipline** — when each artifact is used, so the working deck stops leaking into exec rooms ## Required Inputs Ask for these if not provided: - **The working deck (or analysis)** — the source material; the cut is extraction, n
- What This Skill Produces
- Required Inputs
- Framework: The Split Rules
- Output Format
- The Cut (slide order)
- The Compression Map
- The Appendix Plan
- Quality Checks
- Anti-Patterns
What does the exec-vs-working-deck skill do?
Stop presenting the working deck to executives — the two-deck split (answer-first exec cut vs. exploration-rich working deck), the compression rules from 40 slides to 8, and the appendix strategy that keeps the depth one click away. Use when asked turn this analysis into an exec version, my leadership readout went badly, how do I compress 40 slides to 10 minutes, or what do execs actually want in a deck. Produces the exec cut with the answer-first order, the compression map (what survived, where the rest went), and the Q&A appendix plan.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill exec-vs-working-deck --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.