executive-brief-code

Included with Lifetime

$97 forever

Structure engineering communication (PR descriptions, commit messages, RFCs, design docs, architecture decision records, incident escalations, postmortems, status updates to eng leadership) so a busy reviewer or decision-maker can act with minimal cognitive load. Use this in a dev context whenever the user is writing something a human must read and decide on, with requests like "write the PR description", "draft an RFC for this", "I need to escalate this incident", "write up the postmortem", "summarize this change for review", or "write a design doc". Also use when the user names a method directly such as BLUF, SBAR, SCQA, Minto Pyramid, completed staff work, or decision brief. This is the Claude Code version; output is markdown suited to a terminal, repo, or ticket.

Design

What this skill does


# Executive Brief — Code

A reviewer reading your PR, an on-call lead reading your incident page, a staff engineer reading your RFC — all of them are context-switching from something else and have limited time. Structure the artifact so they grasp the point and the ask immediately.

## Workflow

1. **Pick the method.**
   - If the user named one (BLUF, SBAR, SCQA, Minto, completed staff work, decision brief), use it. Manual choice always wins.
   - Otherwise read `references/method-router.md`, then apply the dev-artifact mapping below.

2. **Load the chosen method.** Read its file in `references/` and apply the template.

3. **Write the artifact** as markdown.

## Dev-artifact mapping (auto-routing for code work)

| Artifact | Method | Why |
| :-- | :-- | :-- |
| Commit message, PR title/description, short status to leadership | **BLUF** | Reviewer has context; lead with what changed and why, details below. |
| Incident escalation, paging an on-call, "prod is broken" | **SBAR** | Live problem; receiver needs status + ask before background. |
| RFC, design doc, proposal for an unfamiliar reviewer | **SCQA** opening + **Minto** body | Rebuild context, then structure the argument gap-free. |
| Approval to merge/ship a risky change | **Completed Staff Work** | Present analyzed options + your recommendation; reviewer approves or rejects. |
| Architecture Decision Record, formal choice between approaches | **FM 6-0 Decision Brief** | Formal COA selection; scale depth to the reader's familiarity. |
| Postmortem | **SBAR** (timeline) or **Minto** (analysis) | SBAR for the incident narrative; Minto when the focus is root-cause reasoning + actions. |

The user can always override this mapping by naming a method.

## Code conventions

- **Output markdown** suited to the destination (PR body, `.md` file in the repo, ticket comment). Match the repo's existing doc style if visible.
- **Lead with the bottom line.** First line states what changed / what's broken / what you recommend.
- **Strip insider jargon for the intended reader.** A PR for the whole team needs more context than a comment to a co-author. Define non-obvious terms with a concrete example.
- **Take a position.** A design doc that lists options without a recommendation pushes the thinking back onto the reader — exactly the load this skill removes.
- **Keep code and prose separate.** Put the brief in prose; let code blocks and diffs carry the detail.

## When the input is too thin

If you can't fill the method (unclear what decision is needed, no options analyzed, no failure detail), say what's missing in one line and ask for just that.

Files: 8

Size: 18.3 KB

Complexity: 45/100

Category: Design

Source: https://github.com/thamam/a2x-marketplace/tree/main/plugins/interaction-patterns/skills/executive-brief-code

Related in Design

contribute

Included

Local-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".

Designscripts

architectural-analysis

Included

User-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).

Designscripts

mcp

Included

Model Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.

Designscripts

react-native-skia

Included

Design, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.

Designscripts

plaid

Included

Product Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".

Designscripts

nextjs-framer-motion-animations

Included

Adds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.

Designscripts