← Back to tooling Claude Code · /concept-ideation

Concept-ideation skill

Research to designer-ready in ~20 minutes.

The biggest chore in a growth manager's month is producing ad concepts: research, ideation, copy, and all the ops around them. I wrote the whole task down as a skill. One line kicks it off, and 20 minutes later the concept page, the Drive folder and the designer brief exist, in the client's voice, grounded in real audience language.

2h → 20 min per concept, research to designer-ready handoff

The manual task this skill replaced

Inspirations: Meta, Foreplay, social
What's already working in the account
Winning formats + angles
Combine into 5+ angles and formats
Headline variations
ICPs, dream outcomes, pain points
Full body copy
Notion concept page
Drive folder
Designer brief
Send to the designer
Per-GM extras: approval docs, Sheets
One concept, delivered
ResearchIdeationCopywritingOps & handoffPer-GM extras

13+ steps across 4 tools, mapped before the skill was written. Now the map runs itself in ~20 minutes.

  • 🔍 Inspirations: Meta, Foreplay, social
  • 📈 What's already working in the account
  • 🏆 Winning formats + angles
  • 🧩 Combine into 5+ angles and formats
  • ✍️ Headline variations
  • 🎯 ICPs, dream outcomes, pain points
  • 📝 Full body copy
  • 📄 Notion concept page
  • 📁 Drive folder
  • 🎨 Designer brief
  • 📤 Send to the designer
  • ➕ Per-GM extras: approval docs, Sheets

How a run actually goes

01

One line kicks it off

"/concept-ideation for How to AI", plus a Foreplay ad ID as inspiration if you have one. First thing it does: reads its own rules and IDs, and resolves which growth manager is running it.

The actual one-line prompt that starts a run
The actual one-line prompt that starts a run
02

It interviews you before acting

Two pre-flight questions: how many hook variations (3-5, across confession, peer-to-peer, counterintuitive, identity and specificity angles) and whether you want a client approval doc. No surprises mid-run.

The pre-flight interview
The pre-flight interview
03

Then it researches. 7 sources.

Client Notion page, live website, Reddit/Quora audience language, both Slack channels, the client's own ad account (winning = SPEND, not just KPI), Foreplay competitor swipe, and the latest newsletter analysis.

04

Writes hooks + body in the client's voice, then stops

"Approved to build?" Nothing gets created until I say yes. This is the back-and-forth zone: iterate on any line in plain English.

DCT_167 "The AI Person": 3 hooks + universal body, each with a flow check
DCT_167 "The AI Person": 3 hooks + universal body, each with a flow check
05

One "approved" later: everything built and verified

The internal Notion concept page, the Drive folder with Raw assets + Final output, and the designer brief already filled: reference video, typesetting rules, the 3-column script table. From here it's press a button to the designer and the concept is live in 24h. It even audits itself at the end of every run and lists fixes worth baking back into its own instructions.

The full handoff: concept page, designer brief, Drive folder
The full handoff: concept page, designer brief, Drive folder
06

And it's steerable, not all-or-nothing

Real case: a teammate already had approved copy in a Google Sheet. He didn't need research or copywriting, so he told the skill exactly that, in plain English. A skill is written instructions, not a locked pipeline: enter at any step, skip any step, swap any input.

Steering it, typed in plain English/concept-ideation for Imaging Wire. The copy is already approved
in this Sheet: [link]. Skip the research and the copywriting.
Just run the build steps: internal Notion concept page,
Drive folder, and the designer brief.
Luiz's copy, already done in Sheets. The skill picks up from there.
Luiz's copy, already done in Sheets. The skill picks up from there.

Rules & guardrails straight from the skill instructions

Next tool Canva-AI template skills →