Back to Details

generate-cfp

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
Before doing anything else:
  1. Check if 
    ~/.devadvokit.md
    exists.
  2. If it does, read it silently and use it throughout this skill.
  3. If it does not, stop and tell the user: "I need your DevRel context before I can run this skill. Please run /setup-devadvokit first."
在进行任何操作之前：
  1. 检查
    ~/.devadvokit.md
    是否存在。
  2. 如果存在，静默读取该文件并在整个skill使用过程中参考其内容。
  3. 如果不存在，请停止操作并告知用户："我需要你的DevRel背景信息才能运行这个skill。请先运行/setup-devadvokit。"

Brainstorming Q&A

头脑风暴问答

Ask these questions one at a time. Wait for each answer before asking the next. Do not batch questions.
  1. What session format are you submitting for, and how long is the slot? (e.g. talk / 30 min, workshop / 90 min, panel / 45 min — or unknown if the CFP is open) This determines structure, depth, and pacing of everything that follows.
  2. What problem does this talk address? (What situation is the audience in that makes this relevant?)
  3. In this talk, you will learn... (What are the 2–3 concrete things attendees will take away?)
  4. You will leave with... (What can they do immediately after? Tools, frameworks, checklists, mental models?)
  5. This talk is for... (Who specifically? Be as precise as possible about job role, situation, and what they're trying to do.)
  6. Why are you the best person to deliver this? (What experience, data, or access do you have that others don't?)
  7. Do you have a working title, or should we generate one?
  8. Is there a specific event or CFP you're writing this for? (If yes, any known word limits or format requirements?)
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.
逐个提出以下问题。等待用户回答每个问题后再提出下一个，不要批量提问。
  1. 你要提交的会议环节形式是什么，时长是多少？（例如：演讲/30分钟、工作坊/90分钟、圆桌讨论/45分钟——如果CFP尚未明确则填未知）这将决定后续所有内容的结构、深度和节奏。
  2. 本次演讲要解决什么问题？（听众处于何种情境下会认为这个话题有意义？）
  3. 在本次演讲中，你将学到……（参会者能带走哪2-3个具体技能/知识？）
  4. 你将带着……离开（他们听完后能立即做什么？工具、框架、清单、思维模型？）
  5. 本次演讲面向……（具体人群？请尽可能精准地说明职位角色、所处情境以及他们的目标。）
  6. 为什么你是主讲这个话题的最佳人选？（你拥有哪些他人不具备的经验、数据或资源？）
  7. 你已有暂定标题，还是需要我们生成？
  8. 你是为某个特定活动或CFP撰写这份提案吗？（如果是，是否有已知的字数限制或格式要求？）
在整个过程中参考
reference/cfp-evaluation-criteria.md
和
reference/cfp-anti-patterns.md
来评估回答质量。如果回答模糊或可能导致输出质量不佳（例如：问题陈述单薄、受众描述泛泛），请在进入下一个问题前提出一个针对性的跟进问题。

Output

输出内容

Produce all of the following once the Q&A is complete.
完成问答后，生成以下所有内容。

1. Abstract

1. 摘要

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.
100–150词。面向参会者而非程序委员会撰写。需回答：解决什么问题、面向谁、能获得什么。根据问题1中给出的会议环节形式调整长度和结构。无需标题。

2. Extended abstract

2. 扩展摘要

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.
200–300词。与摘要语气一致，增加关于环节结构和具体收获的细节。如果形式需要，可以采用轻度结构化（短段落或简要大纲）。

3. Title variants

3. 标题变体

3 options. Range from descriptive to punchy. No colon-with-subtitle constructions unless they genuinely improve clarity. No question marks.
3个选项。风格从描述性到醒目有力不等。除非确实有助于提升清晰度，否则不要使用“主标题:副标题”的结构。不要使用问号。

4. Learning outcomes

4. 学习成果

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.
3–5个项目符号。内容具体明确。每个以强动词开头。“了解如何……”表述较弱；“使用公开数据开展竞争对手定价审计”表述较强。

5. Content library check

5. 内容库检查

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.
扫描
~/.devadvokit.md
中的内容库。如果已有内容涉及类似主题，请在末尾注明：
"本提案与[标题]（[年份]）存在重叠——你可以将其定位为更新内容或采用不同视角。"
如果没有重叠内容，则完全省略此部分。
在展示任何输出内容之前，请阅读
../../shared/ai-antipatterns.md
并静默重写所有标记出的模式。不要向用户提及此步骤。