New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Decision Memo Builder

by sruthir28 in sruthir28/enterprise-ai-skills

Builds a 1-page decision memo (context → options → recommendation → risks → ask) enforcing McKinsey memo DNA — brutal brevity, SCP storyline clarity, decision-forcing output, evidence density.

MITAuto-check passed

Install Decision Memo Builder

skills CLI
$ npx skills add sruthir28/enterprise-ai-skills --skill decision-memo-builder -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install sruthir28/enterprise-ai-skills decision-memo-builder --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/sruthir28/enterprise-ai-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/decision-memo-builder .claude/skills/decision-memo-builder && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
decision-memo-builder
GitHub stars
148
Token cost
~1.7k tokens
SKILL.md length
928 words
Files
1
Skills in repo
14
Repo updated
First seen
Licence
MIT

At a glance

Builds a 1-page decision memo (context → options → recommendation → risks → ask) enforcing McKinsey memo DNA — brutal brevity, SCP storyline clarity, decision-forcing output, evidence density.

  • Works in 4 steps: Brutal brevity — 1 page, ~400 words max.… → Storyline clarity (SCP) — Situation →… → Decision-forcing — Last line is a yes/no… → …
  • Drafting a memo for a leadership decision
  • SKILL.md covers Memo DNA — four non-negotiables, Structure, Process and Worked Example 1: Tooling…, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Decision Memo Builder is an agent skill from sruthir28/enterprise-ai-skills. Builds a 1-page decision memo (context → options → recommendation → risks → ask) enforcing McKinsey memo DNA — brutal brevity, SCP storyline clarity, decision-forcing output, evidence density. Use when drafting a memo for a leadership decision, a scope cut, a buy/build/partner call, a roadmap slip, or any "should we X?" moment that needs a yes/no from a specific person by a specific date.

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Open-source AI skills for enterprise professionals. McKinsey consulting frameworks, PM workflows, and practical tools. Currently for Claude, expanding to other LLMs. The licence is MIT.

When your agent uses it

  • Drafting a memo for a leadership decision
  • A buy/build/partner call
  • Any should we X? moment that needs a yes/no from a specific person by a specific date

Example prompts

  • “should we X?”
  • “Use the decision-memo-builder skill to build a 1-page decision memo (context → options → recommendation → risks → ask) enforcing McKinsey memo DNA —…”
  • “/decision-memo-builder”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Brutal brevity — 1 page, ~400 words max. Every sentence earns its place or gets cut.
  2. Storyline clarity (SCP) — Situation → Complication → Resolution flow. Reader never asks "so what?"
  3. Decision-forcing — Last line is a yes/no ask with owner and date. Never "further analysis needed."
  4. Evidence density — Every claim backed by a number, quote, or source. No adjectives doing load-bearing work.

What it can do on your machine

Read from SKILL.md and the folder at commit ae8fe60. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Decision Memo Builder loads about 1.7k tokens when it runs. Until then it costs about 103 tokens; SKILL.md has 928 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~103
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from sruthir28/enterprise-ai-skills at commit ae8fe60, republished under its MIT licence (© sruthir28). 928 words, ~1,695 tokens.

Download SKILL.mdSave it as .claude/skills/decision-memo-builder/SKILL.md (or your agent's skills folder).
name
decision-memo-builder
description
Builds a 1-page decision memo (context → options → recommendation → risks → ask) enforcing McKinsey memo DNA — brutal brevity, SCP storyline clarity, decision-forcing output, evidence density. Use when drafting a memo for a leadership decision, a scope cut, a buy/build/partner call, a roadmap slip, or any "should we X?" moment that needs a yes/no from a specific person by a specific date.

Decision Memo Builder

A 1-page memo that forces a decision. Not a status update. Not a brief. Not a FYI. The reader walks away knowing exactly what they are being asked to approve, by when, and why.

Memo DNA — four non-negotiables

Every decision memo must pass all four. If the draft fails one, rewrite. Do not ship a memo that fails Memo DNA.

  1. Brutal brevity — 1 page, ~400 words max. Every sentence earns its place or gets cut.
  2. Storyline clarity (SCP) — Situation → Complication → Resolution flow. Reader never asks "so what?"
  3. Decision-forcing — Last line is a yes/no ask with owner and date. Never "further analysis needed."
  4. Evidence density — Every claim backed by a number, quote, or source. No adjectives doing load-bearing work.

Structure

Title (≤10 words)

Name the decision, not the topic.

  • ✅ "Sunset legacy reporting engine by Q3"
  • ❌ "Reporting strategy update"
Context (3–4 sentences)

State of the world before the ask. Facts only. Baseline numbers. No history-of-the-universe framing.

Complication (2–3 sentences)

What changed, or what's at risk if we don't decide now. Include the number that makes this urgent.

  • ✅ "Usage down 15% QoQ; 3 enterprise deals ($1.2M) flagged the gap in Q1 QBRs."
  • ❌ "Usage has been declining and customers are concerned."
Options (2–3 options, 1–2 lines each)

Mutually exclusive. Each option gets:

  • Name
  • One-line description
  • The single most important trade-off (cost, time, or risk)

Do not sneak a recommendation in here.

Recommendation (1 short paragraph)

State the chosen option and why it wins on the decision criteria that matter most. Cite the evidence that tips the call.

Risks & Mitigations (≤3 bullets)

The top 3 things that could go wrong, each paired with a 1-line mitigation. Not a risk inventory — the three the reader would actually ask about.

The Ask (1 line)

A specific yes/no request with an owner and a date.

  • ✅ "Approve sunset by EOD Friday; Sarah owns migration plan by 5/1."
  • ❌ "Let's discuss next steps."

Process

  1. Interview before drafting. Ask the user:

    • Who is the reader? (CEO, VP, peer)
    • What decision do they need to make?
    • What's the deadline?
    • What are the real 2–3 options, and which do you think wins?
    • What evidence do you have? (Numbers, quotes, benchmarks)

  2. Draft in Memo DNA order. Title → Context → Complication → Options → Recommendation → Risks → Ask.

  3. Run the four tests. For each section, confirm it passes Memo DNA. Flag any that fail.

  4. Cut 30%. First drafts are always too long. Strip adjectives, hedging ("potentially," "may," "could possibly"), and throat-clearing.

  5. Stress-test the ask. Can the reader answer yes or no from the memo alone? If not, sharpen.

Worked Example 1: Tooling Migration

Title Switch engineering + product from Jira to Linear by 5/30

Context ~60 engineers and PMs on Jira today. $48K/yr in licenses. 4 active projects, custom workflows, 6 years of history. Engineering NPS on tooling = 4/10 in the Q1 survey.

Complication Jira admin role has been open 4 months; no single owner maintaining workflows. Two teams (Growth, Platform) ran Linear pilots in Q1 — 30% faster issue creation, 50% less "which field is required" confusion. Renewal is due 5/30 and auto-renews at +12%.

Options

  1. Stay on Jira — $54K next year, zero migration cost, continued tooling friction.
  2. Migrate to Linear — $36K/yr, ~6 weeks of migration work, cleaner UX, loses some Jira-specific reports.
  3. Run Linear + Jira in parallel for 6 months — hedged, doubled cost ($90K), splits team context.

Recommendation Migrate to Linear. Saves $18K/yr, ends the 4-month admin vacancy, and two pilot teams already validate the productivity win (60 people × 1 hr/wk saved ≈ $300K/yr loaded). The "lost reports" risk is low — exec dashboards already live in Looker, not Jira.

Risks & Mitigations

  • 6 years of Jira history → export to a read-only archive; no lift-and-shift.
  • Custom workflow loss → document the top 3 workflows, rebuild in Linear before cutover.
  • Team resistance → give Growth + Platform leads ownership of internal comms.

The Ask Approve Linear migration by 5/30. Priya owns migration plan; Alex cancels Jira renewal.

Show full SKILL.md (273 more words)Show less

Worked Example 2: Scope Cut

Title Cut AI-tagging from v2 launch — approve by EOD

Context v2 is committed for 5/15. Current scope: 8 features, ~1,800 engineer-hours estimated. Team capacity = 1,400 hours remaining.

Complication We're 400 hours over. AI-tagging alone = 350 hours and blocks 3 other teams' integrations if it slips.

Options

  1. Ship all 8, slip 3 weeks — breaks GTM commits to 4 design partners.
  2. Cut AI-tagging, ship 5/15 — scope fits, saves 350 hrs, feature defers 6 weeks.
  3. Cut 2 smaller features, keep AI-tagging — fits scope but breaks onboarding funnel.

Recommendation Cut AI-tagging. Launch date > this feature. AI-tagging ranked #6 in customer survey (n=42). Cutting the 2 smaller features would break a conversion funnel we validated last quarter (+18% activation).

Risks & Mitigations

  • GTM already promised AI-tagging → update positioning memo this week.
  • Team morale dip → announce v2.1 date (7/1) alongside the cut.
  • Competitor parity → no competitor ships it today; 6-week delay = low risk.

The Ask Approve cutting AI-tagging from v2 by EOD. Alex updates GTM narrative; Jordan re-plans v2.1.

Anti-patterns

  • ❌ Bullet-point soup with no storyline
  • ❌ "We should consider..." — decision-averse hedging
  • ❌ Missing numbers — "significant impact," "major risk," "strong signal"
  • ❌ Recommendation leaked into the Options section
  • ❌ Ask that's just "discuss next steps"
  • ❌ > 1 page — if you need more, split into memo + appendix

When to Use

  • Leadership decision requests (buy/build, hire, cut, pivot)
  • Roadmap calls (ship / slip / cut)
  • Scope trade-offs (cut X to save Y)
  • Strategic pivots
  • Any moment a peer or exec needs a yes/no from you

When NOT to Use

  • FYI updates → use a status note
  • Brainstorms → use issue-tree-builder
  • Broader strategic narratives → use scpr-framework
  • Presentations → use storyline-builder
  • Post-review quality check → pair with mckinsey-critic

© sruthir28, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in decision-memo-builder of sruthir28/enterprise-ai-skills.

Open the folder on GitHubat commit ae8fe60

Compare with similar skills

Decision Memo Builder next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Decision Memo Builder compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Decision Memo Builder this skillsruthir28/enterprise-ai-skills148—~1.7kAutomated safety check: PassMIT
Optionsasgeirtj/system_prompts_leaks69k—~918Automated safety check: PassCC0-1.0
Memoanthropics/claude-for-legal9.6k3 repos~2.5kAutomated safety check: PassApache-2.0
Team Builderaffaan-m/ECC276k1 repos~1.8kAutomated safety check: PassMIT
Team Builderaffaan-m/ECC276k1 repos~808Automated safety check: PassMIT
Dashboard Builderaffaan-m/ECC276k—~221Automated safety check: PassMIT

Similar skills

  • Options

    asgeirtj/system_prompts_leaks

    Present multiple design options as a vertical stack of anchored turns

    69k GitHub stars~918 tokensUpdated yesterday
    Auto-check passed

  • Memo

    anthropics/claude-for-legal

    Official

    IRAC-scaffolded case analysis memo with research gaps flagged — the scaffold, not the analysis.

    9.6k GitHub starsUsed in 3 repos~2.5k tokens
    DevelopmentAuto-check passed

  • Team Builder

    affaan-m/ECC

    Interactive picker that discovers available agent personas via the claude agents command and agents/ markdown globs, groups them into domains, has the user select up to five, dispatches them in…

    276k GitHub starsUsed in 1 repo~1.8k tokens
    Agent WorkflowsAuto-check passed

  • Team Builder

    affaan-m/ECC

    用于组合和派遣并行团队的交互式代理选择器

    276k GitHub starsUsed in 1 repo~808 tokens
    Auto-check passed

  • Dashboard Builder

    affaan-m/ECC

    Grafana、SigNoz、および同様のプラットフォーム用の実際のオペレータ質問に答える監視ダッシュボードを構築します。メトリクスを虚栄ボードではなく機能するダッシュボードに変える場合に使用します。

    276k GitHub stars~221 tokensUpdated 4 days ago
    DevOps & CloudAuto-check passed

  • Dashboard Builder

    affaan-m/ECC

    为 Grafana、SigNoz 等平台构建能够回答实际运维人员问题的监控仪表板。适用于将指标转化为可用的仪表板，而非华而不实的展示板。

    276k GitHub stars~279 tokensUpdated 4 days ago
    DevOps & CloudAuto-check passed

More from sruthir28/enterprise-ai-skills

All 14 skills in this repo

  • Storyline Builder

    sruthir28/enterprise-ai-skills

    McKinsey-style storyline framework for building presentation decks.

    148 GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed

  • AI Use Case Scorer

    sruthir28/enterprise-ai-skills

    Score and prioritize AI use cases for your own job. An agent skill from sruthir28/enterprise-ai-skills.

    148 GitHub stars~1.5k tokensUpdated 1 mo ago
    Auto-check passed

  • Deck Pipeline

    sruthir28/enterprise-ai-skills

    Multi-agent pipeline that builds a polished presentation deck from a single topic.

    148 GitHub stars~2.2k tokensUpdated 1 mo ago
    Auto-check passed

  • Issue Tree Builder

    sruthir28/enterprise-ai-skills

    McKinsey-style issue tree framework for breaking down complex problems into MECE (Mutually Exclusive, Collectively Exhaustive) components.

    148 GitHub stars~1.9k tokensUpdated 1 mo ago
    Auto-check passed

  • Mckinsey Charts

    sruthir28/enterprise-ai-skills

    Generate McKinsey-style consulting charts as native python-pptx objects (editable inside PowerPoint).

    148 GitHub stars~999 tokensUpdated 1 mo ago
    Auto-check passed

  • Scpr Framework

    sruthir28/enterprise-ai-skills

    SCPR (Situation-Complication-Problem-Recommendation) framework for structured problem solving and executive communication.

    148 GitHub stars~1.2k tokensUpdated 1 mo ago
    Auto-check passed

Questions about Decision Memo Builder

What does Decision Memo Builder do?

Builds a 1-page decision memo (context → options → recommendation → risks → ask) enforcing McKinsey memo DNA — brutal brevity, SCP storyline clarity, decision-forcing output, evidence density. Decision Memo Builder is an agent skill from sruthir28/enterprise-ai-skills. Builds a 1-page decision memo (context → options → recommendation → risks → ask) enforcing McKinsey memo DNA — brutal brevity, SCP storyline clarity, decision-forcing output, evidence density.

When should I use Decision Memo Builder?

Decision Memo Builder fits situations like: drafting a memo for a leadership decision; A buy/build/partner call; any should we X? moment that needs a yes/no from a specific person by a specific date.

How do I install Decision Memo Builder in Claude Code?

Run `npx skills add sruthir28/enterprise-ai-skills --skill decision-memo-builder -a claude-code`. Or copy the skill folder (decision-memo-builder in sruthir28/enterprise-ai-skills) into .claude/skills/decision-memo-builder in your project. Claude Code loads it when a task matches its description.

How do I install Decision Memo Builder in Codex?

Run `npx skills add sruthir28/enterprise-ai-skills --skill decision-memo-builder -a codex`. Or copy the skill folder (decision-memo-builder in sruthir28/enterprise-ai-skills) into .agents/skills/decision-memo-builder in your project. Codex loads it when a task matches its description.

Can I use Decision Memo Builder in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sruthir28/enterprise-ai-skills --skill decision-memo-builder -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/decision-memo-builder, .gemini/skills/decision-memo-builder, .github/skills/decision-memo-builder and .opencode/skills/decision-memo-builder in your project.

What does Decision Memo Builder need to run?

SKILL.md names no scripts, command-line tools or credentials: Decision Memo Builder is instructions for the agent only.

Does Decision Memo Builder access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Decision Memo Builder safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Decision Memo Builder use?

Decision Memo Builder is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Decision Memo Builder use?

About 1.7k tokens (SKILL.md is roughly 6.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Decision Memo Builder?

Skills that share tags, products or a category with Decision Memo Builder: Options (asgeirtj/system_prompts_leaks, 69k stars), Memo (anthropics/claude-for-legal, 9.6k stars), Team Builder (affaan-m/ECC, 276k stars) and Team Builder (affaan-m/ECC, 276k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Decision Memo Builder?

sruthir28 (a GitHub user) maintains it in sruthir28/enterprise-ai-skills, which has 148 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on September 1, 2026.

Source: sruthir28/enterprise-ai-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.