Brainstorm and develop angles for a new newsletter issue — grounded in the writer's Brief (the through-line, lenses, topics, and objectives) and their archive (to avoid repeating past coverage). A PRE-SET, context-aware ideation partner, specific to the newsletter with zero setup. It sharpens the writer's thinking; it does not write the piece (D21). Use for "help me brainstorm", "ideas for the next issue", "what should I write about", "develop this angle", "is this worth a piece".
Installs into .claude/skills of the current project.
Are you the author of Brainstorm?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/artifacts7-brainstorm)
---
name: brainstorm
description: >
Brainstorm and develop angles for a new newsletter issue — grounded in the writer's Brief
(the through-line, lenses, topics, and objectives) and their archive (to avoid repeating past
coverage). A PRE-SET, context-aware ideation partner, specific to the newsletter with zero setup.
It sharpens the writer's thinking; it does not write the piece (D21). Use for "help me brainstorm",
"ideas for the next issue", "what should I write about", "develop this angle", "is this worth a piece".
---
# Brainstorm — the ideation partner
A pre-set skill that reads the writer's own generated context and helps them find and sharpen
angles. Newsletter-specific automatically — no authoring required (D22).
## Reads
`newsletter-context/newsletter-brief.md` (identity, lenses, objectives) · the corpus/manifest (overlap check) ·
`newsletter-context/voice-profile.md` (what *kind* of angle fits the voice).
## Procedure
1. **Ground in the Brief.** Anchor on the through-line, the signature lenses (the analytical moves),
the core topics, and the **current objectives** (e.g. growth areas the writer flagged in reconcile).
2. **If the writer brings a topic:** find the **interface moment** to lead with (the concrete
screen/feature/decision — the signature open), name who decided, surface the power angle.
Offer 2–3 candidate framings and a *direction* for the governing metaphor — but prompt the
writer for a **real** anchor (a thing they actually saw/used); never hand them an invented simile (naturalness, D21).
3. **If the writer is blank:** propose angles from the objectives + current news in the newsletter's
lane, each shaped as *interface moment → power*. **Flag overlap** with past issues (cite slugs).
4. **Pressure-test each angle:** Does it fit the Brief? Is it a real interface moment? Been done before?
What's the *"So, what?"* — the argument under the report?
## Output
A few developed angles (framing · interface moment · the open question it raises), overlap flags,
and prompts for the writer's own next move. **Assist only** — the writer chooses and writes.
## Boundary (D21)
Ideation partner, not ghostwriter. It surfaces, grounds, and sharpens; it does not produce the draft.
---
_**Language:** if the newsletter isn't in English, converse with the writer — and write outputs — in the newsletter's language._
