name: framework-note
description: Turn the name of a decision-making or mental-model framework (Eisenhower Matrix, premortem, OODA loop, etc.) into a source-verified 4-part reference card — definition, how to use it, a real applied example, and its limits — with every factual claim traced to a real, cited source instead of remembered-and-possibly-wrong summary. Use when asked to explain a framework, create a reference card for a mental model, or summarize a decision-making technique with real sources.
trigger: The user names a specific decision-making framework, mental model, or methodology and asks for an explanation, summary, reference card, or cheat sheet — especially when they want it grounded in real sources rather than a generic paraphrase.
version: 1.0.0
compatible_agents: [claude-code, codex, openclaw]

Framework Note — a source-verified 4-part card, not a remembered summary

Explaining a named framework from memory risks two failure modes: misattributing who created it or
when, and flattening real nuance into a generic paraphrase that could describe almost any
framework. This Skill fixes both by building the card only from claims traced to something you can
actually verify.

Ground rules (apply throughout)

1. Every factual claim needs a traceable source — the origin, the year, who uses it, and any
   data point. If you have web access, fetch/search for the actual originating text (a book
   excerpt, an article, an interview) rather than relying on trained-in memory. If you don't have
   web access or can't verify a specific claim, say so explicitly and either omit it or label it
   "unverified — from general knowledge, not independently confirmed" rather than presenting it as
   settled fact.
2. Quote sparingly and mark quote type. Short direct quotes (a sentence or phrase) are fine with
   attribution; do not reproduce large excerpts of copyrighted text (books, paywalled articles).
   For anything beyond a short quote, paraphrase and cite instead. Tag every borrowed claim as
   (quote), (paraphrase), or (unverified).
3. Paywalled sources: if the original is paywalled (e.g. HBR), you may cite and briefly quote
   from publicly available summaries or abstracts, but say plainly that the full original wasn't
   directly accessible.
4. No personal criticism. If part of the note involves a critique (e.g. a common mistranslation
   or misapplication of the framework), phrase it about the idea, not a named individual — don't
   single out a specific person or author as having gotten it wrong.

Step 1 — Definition

State what the framework is, who originated it (person/organization) and roughly when, sourced to
something checkable. If origin is genuinely disputed or unclear, say so rather than picking one
account and presenting it as fact.

Step 2 — How to use it

The actual procedure: the steps or structure someone follows to apply it. This is usually
describable from the framework's own definition and doesn't always need a separate citation beyond
the definition's source — but if you're citing a specific "how-to" variant (e.g. a particular
consultant's step breakdown), attribute that too.

Step 3 — Applied example

A real, named instance of the framework being used — a specific person, company, or documented case
— not a generic hypothetical ("imagine a manager who..."). If you can't find or verify a real
example, say so and offer a clearly-labeled illustrative (not real) example instead rather than
implying it's documented.

Step 4 — Limits

Where the framework breaks down or gets misapplied — genuine limitations, not a token disclaimer.
If there's a well-known critique or common misuse, describe it about the idea/pattern rather than
naming who made the mistake.

Output format

## [Framework Name]

### Definition
[definition] — Source: [name, year] (quote/paraphrase/unverified)

### How to Use It
1. ...
2. ...

### Applied Example
[real named example] — Source: [name, year] (quote/paraphrase/unverified)
(or: "No verifiable real-world example found — illustrative example below is not documented:" ...)

### Limits
[where it breaks down, genuinely]

### Sources
- [Source 1 — year] — [link if available]
- [Source 2 — year] — [link if available]

Handling sensitive info

This Skill fetches whatever sources it can find for the named framework — no personal or
confidential information is expected as input, but if you provide proprietary internal context
(e.g. "how we use this framework at [company]"), treat that as context only and don't echo it back
beyond what's needed.