generate-bio

name	generate-bio
description	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.

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."

---

Q&A

Ask these questions one at a time. Wait for each answer before asking the next.

1. What's this bio for? (e.g. conference speaker profile, LinkedIn about section, company team page, personal website, podcast guest intro, book jacket — be specific if you can)

2. How long should it be? Choose one:

   • One-liner — a single sentence (~20–30 words)
   • Short — one tight paragraph (~50–75 words)
   • Medium — two paragraphs (~100–150 words)
   • Long — three or more paragraphs (~200–300 words) — or give a specific word count or character limit if the platform requires one.

3. First person ("I'm a developer advocate...") or third person ("Jane is a developer advocate...")?

4. On a scale of 1 to 5, how much should this bio focus on your current employer?

   • 1 — employer-led: opens with your company, leads with what you do there, frames your expertise through your current role. Suits company team pages, sponsored content, and employer-brand contexts.
   • 3 — balanced: current role is present and clear, but career-wide expertise and your broader identity carry equal weight. Suits most conference and speaker bios.
   • 5 — employer-light: current role is mentioned but not the focus. Leads with career-wide expertise, personal brand, and what you're known for across the industry. Suits personal sites, independent speaking, and contexts where you want to be seen as more than your current job.

   Answer with a number. If unsure, 3 is a safe default for most conference bios.

---

Generating the bio

Use the answers to the Q&A and the context from ~/.devadvokit.md to produce the bio. Apply the scale as follows:

Scale 1: Open with the company and current role. Frame expertise in terms of what the speaker does at this employer. Previous roles and career-wide specialisms appear only if space allows, and only in support of the current role. Location and hobbies may appear if the format and length suit it, but the employer is the primary anchor.

Scale 2: Current role and company are prominent and come early, but career-wide expertise begins to share the frame. One or two previous roles or broader specialisms are woven in. The employer is clearly present but the person's experience beyond it starts to show.

Scale 3: Current role is stated clearly but doesn't dominate. Career-wide specialisms, areas of expertise, and what the speaker is known for across the industry carry equal weight. The employer is mentioned once, in context, without being repeated or emphasised. Location and personal detail may appear depending on length.

Scale 4: Lead with career-wide expertise and what the speaker is known for. Current role appears, but later and without emphasis — one mention, no repetition. Previous roles and cross-career themes are as prominent or more prominent than the current position.

Scale 5: The current employer is noted but not foregrounded. Open with the speaker's identity, expertise, and reputation in the field — not their job title. The bio could largely hold if they changed employers tomorrow. Use the full breadth of career-wide specialisms, notable work, and personal context from ~/.devadvokit.md.

Calibrate length and structure to the format given in question 1 — a conference speaker bio reads differently from a LinkedIn about section. Consult reference/bio-contexts.md for format-specific guidance.

---

Output

Produce one bio matching the requested parameters.

Then offer: "Want me to try a different length, person, or employer focus? I can also generate a second variant at a different scale point if you want to compare how the framing shifts."

---

Before presenting any output, read ../../shared/ai-antipatterns.md and silently rewrite any flagged patterns. Do not mention this step to the user.