菜单
Use when the user needs to create a presentation, pitch deck, slide deck, or visual summary about a project, codebase, website, or topic. Triggers on requests like 'build a deck', 'create a presentation', 'make slides about', or 'pitch deck for'.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Get a second opinion on your current implementation plan by sending it to Codex for independent review. Use after brainstorming, after writing a plan, or when you want to iterate on a plan before execution. Triggers on 'get a second opinion', 'review plan with codex', 'codex review', or 'iterate on plan'.
Use when reviewing an implementation plan document (docs/superpowers/plans/*.md or similar) for LLM-style overengineering before implementation. Runs a rubric-driven Claude pass plus a Codex adversarial pass, merges findings, and proposes specific edits to slim the plan. Triggers on 'check this plan for bloat', 'is this overengineered', 'detect overengineering', or invoked as /detect-overengineering.
Use when the user wants a git-history health check of an unfamiliar or inherited repository — triggers on "git recon", "codebase health check", "analyze this repo's history", "where are the landmines", or onboarding/due-diligence framing. Do NOT use for architecture review, bug-fixing, or feature work; this skill reads history, not code. Main-thread only — subagents dispatched to execute a delegated task must NOT invoke this skill.
Use when reading or reporting what automated PR reviewers left before merging — Codex (`chatgpt-codex-connector`) and an Architecture-Review / SAR GitHub Action (`github-actions[bot]`). Triggers on "what did the bots say", before declaring a PR done or merging, or when a Codex finding or clean verdict seems missing because `gh pr view --json comments` came back empty. Read-only (does not commit or push); for auto-fixing PR feedback use `/pr-fix` instead.
| name | presentation-blueprint |
| description | Use when the user needs to create a presentation, pitch deck, slide deck, or visual summary about a project, codebase, website, or topic. Triggers on requests like 'build a deck', 'create a presentation', 'make slides about', or 'pitch deck for'. |
Fortune 500 presentation consultant. Pipeline: analyze, strategize, outline, style, render.
Verify document-skills:pptx is available. If missing, instruct user to install it and stop.
| Type | Triggers | Slides |
|---|---|---|
| Pitch | fundraise, investors, startup | 10-12 |
| Technical | architecture, system design, API | 15-20 |
| Update | status, quarterly, progress | 5-8 |
| General | summarize, overview, "about" | 10-12 |
digraph { rankdir=LR; Analysis->Strategy->Outline->Style->Render; Outline->Strategy [label="reject\nmax 3"]; Outline [label="Outline\n(approval gate)"]; Style [label="Style\n(approval gate)"]; }
Per ./source-analysis.md. Sources: codebase (README, docs, package.json, CLAUDE.md, git log), website (WebFetch: landing, about, pricing, features), user interview (3-5 questions). If a source fails, note and continue. Interview alone is minimum viable path.
Per ./narrative-frameworks.md. Define: objective, audience, key message, ask, narrative arc. Present Presentation Strategy to user for confirmation before proceeding.
Format: Slide N: [Type] — "Key message". Approval gate: user must approve. Max 3 revision loops, then offer "start over" or "abort". Warn at 25+ slides.
| Type | Default |
|---|---|
| Pitch | Dark, bold, high-contrast |
| Technical | Clean, structured, diagram-heavy |
| Update | Data-heavy, minimal decoration |
Approval gate. Pass style label + parameters to pptx skill. No intermediate document.
Delegate to document-skills:pptx html2pptx workflow. Reference ./slide-archetypes.md for layouts. No speaker notes (async-first). No incremental updates — each invocation produces one complete deck. Rendering errors surfaced by pptx skill.
| Never | Why |
|---|---|
| Fabricate metrics | Destroys credibility |
| Skip approval gates | User loses control |
| Generate filler slides | Wastes attention |
| Include secrets/API keys | Security breach |
| Render before approval | Wrong output |
| Assume style without confirmation | Style mismatch |