メニュー
Generate a complete conference proposal through a structured brainstorming Q&A. Produces abstract, extended abstract, title variants, and learning outcomes — calibrated to the session format and grounded in your DevRel context.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when you have a single piece of content (blog post, talk, case study, docs PR) and want to extract multiple content angles from it — abstraction ladders, audience pivots, controversy checks, and hidden assumptions that could each become their own piece.
Use when you want to discover content series across your existing work — finds clusters by theme rather than topic, identifies repeated points from different angles, flags incomplete arcs, and suggests series framing that makes relationships explicit.
Use when you've delivered a talk and want to convert it into blog posts, social content, newsletter sections, and republishing pitches — or when you have presentation materials (slides, transcript, speaker notes) that could reach wider audiences. Produces multiple content pieces from a single talk.
Use when you've solved a user problem, answered a support question, or helped someone with a technical issue and want to turn it into shareable content. Produces both short-form "TIL" and long-form fully-contextualized pieces, plus recommends the right format (docs, blog, talk).
Turn a CFP submission into a structured talk outline with section timings, theory/practical balance, demo risk assessments, fallback plans, and Patrick Winston opening/close principles applied throughout.
Generate a speaker or author bio through a short Q&A. Controls for length, person (first or third), and a slider for how much to centre the current employer vs. broader career and personal brand.
| name | generate-cfp |
| description | Generate a complete conference proposal through a structured brainstorming Q&A. Produces abstract, extended abstract, title variants, and learning outcomes — calibrated to the session format and grounded in your DevRel context. |
Before doing anything else:
~/.devadvokit.md exists.Ask these questions one at a time. Wait for each answer before asking the next. Do not batch questions.
Consult reference/cfp-evaluation-criteria.md and reference/cfp-anti-patterns.md throughout to assess answer quality. If an answer is vague or likely to produce weak output (e.g. a thin problem statement, a generic audience description), ask one focused follow-up question before moving on.
Produce all of the following once the Q&A is complete.
100–150 words. Written for the attendee, not the programme committee. Answers: what's the problem, who's it for, what will they get. Calibrate length and structure to the session format given in question 1. No headers.
200–300 words. Same voice as the abstract, more detail on the session structure and specific takeaways. Can use light structure (short paragraphs or a brief outline) if the format warrants it.
3 options. Range from descriptive to punchy. No colon-with-subtitle constructions unless they genuinely improve clarity. No question marks.
3–5 bullet points. Concrete and specific. Each starts with a strong verb. "Understand how to..." is weak; "Run a competitor pricing audit using publicly available data" is strong.
Scan the content library in ~/.devadvokit.md. If any existing content covers similar ground, note it at the end:
"This overlaps with [title] ([year]) — you may want to position this as an update or take a different angle."
If nothing overlaps, omit this section entirely.
Before presenting any output, read ../../shared/ai-antipatterns.md and silently rewrite any flagged patterns. Do not mention this step to the user.