outline · git:20261113.8af5195 · 2026-11-13 · sha256 f67f378d8d341614

outline git:20261113.8af5195A

Immutable. This exact content never changes and is served at /api/v1/blob/f67f378d8d341614.

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_jlmd2gwivucimdi3/f67f378d8d341614871abf15d7a58e8c82313e822c1c724aaaa3f8a0ec46502e.json

Then /plugin install outline@markdownregistry-jlmd2gwivucimdi3 in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.

---
name: outline
description: >-
  Use this when turning a seed, interview, or set of facts into a writing plan
  before drafting an article.
---
# Outline

Turn raw material (a seed idea, interview notes, a pile of facts) into a plan the writer can approve. No prose yet.

## Start with one sentence

Write the claim the piece makes and the one thing a reader will learn. If you cannot, ask the writer the question that would unlock it. Everything below serves that sentence.

## Pick a shape

Choose the shape that fits the material, and say why:

- **Story to mechanism.** A specific moment, the tension it shows, what explains it, the evidence, what the reader can do, a return to the moment. Good default for essays and X Articles.
- **Answer first.** The conclusion, then the reasons in order of weight, then caveats. Good for busy readers, docs, and decisions.
- **Teardown.** A thing, its parts one at a time, the verdict. Good for product or launch analysis.
- **Changed my mind.** What I believed, what I saw, what I believe now.

Don't force every section into the same pattern. Give heavy sections more beats and light ones fewer.

## The plan

For each section: a working heading, the job it does in one line, the facts or examples it will use, and its rough length.

Also include:

- **Two or three openings,** each built from something real in the material (a moment, a number, a quote), not "start with an anecdote".
- **Gaps.** Every missing number, quote, source, or experience, marked `[GAP: ...]`. Never fill one by guessing.
- **Cut list.** Material that is true but off the point. Park it so the writer can see it was not lost.

## Hand-off

Present the plan and wait for a yes. Expect the plan to move once drafting starts; a lot of the thinking happens in the draft. After sign-off the chain is draft, source-check, no-ai-slop.

## Inspired by

- [Nadiem Mahmoud, outline](https://github.com/nadiem99/claude-writing-skills/blob/5b52111e1bd30e93643929f17155e82aa26f771f/skills/pipeline/outline/SKILL.md) (MIT). Does well: concrete hook options, a teach test, varied section shapes, and approval before drafting. Missing: one narrative arc for every piece, and it depends on its vault folders and publication pillars.
- [Paul Graham, Writing, Briefly](https://www.paulgraham.com/writing44.html). Does well: warns that detailed outlines aren't always worth it and that most ideas arrive while writing. Missing: no planning method at all.
- [Google Technical Writing Two, Organizing large documents](https://developers.google.com/tech-writing/two/large-docs). Does well: introduce information where the reader needs it, state what the document does not cover, and check the finished draft against the outline. Missing: written for technical docs, with nothing on hooks, story, or evidence gaps.

## What this version adds

- A one-sentence claim before any structure.
- Four named shapes to pick from, with a reason, instead of one arc (a habit from Dani's own post workflow, which rotates shapes).
- A cut list so off-point material is parked, not lost, and an explicit note that the plan will change during drafting.