CFP Submissions

Start with the supplied venue requirements and the closest approved sessions catalog entry. Gather missing topic, audience, purpose, duration, scope, submission limits, and speaker facts one question at a time. Ask only about missing inputs; do not require the deck architecture interview.

Load voice examples and confirmed intent from the rhetoric summary and profile. Do not consume catalog-derived speaker history or infer novelty from past entries.

Draft title, abstract, key takeaways, and speaker bio. Follow the venue's word and field limits; when none are provided, offer a 200–300-word abstract and 3–5 specific takeaways. Keep promised demos, scope, and audience outcomes consistent with the proposed talk. Do not invent credentials, shipped demos, or speaker facts.

If no outline exists, a prose section outline is enough for a submission. An existing outline may inform scope, but it is not a prerequisite and this skill does not write or migrate it. For talk development, invoke Skill(skill: "presentation-creator") only when requested and finish that submission action after returning its materials.

Iterate on author feedback. Once the materials are approved, use catalog.md to save the approved version. A full-talk handoff already carrying approved text proceeds directly to the catalog operation.