turn-incident-into-content

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

---

What NOT to Do

This skill produces content directions — not finished publication drafts. Specifically:

• No polished blog posts — you're creating frameworks for future pieces
• No commit-ready docs PRs — this gives you the structure and says where docs should be updated, not the PR text itself
• No social media threads — use /repurpose-talk for that workflow

The goal is extracting the reusable lesson from a specific incident.

---

Q&A

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

1. What was the problem? Describe what the user was trying to do and what they ran into. Be specific — the actual error message, the unexpected behavior, what was confusing.

2. What did you try? Walk me through your debugging process. What solutions did you attempt? What didn't work? This shows the problem-solving journey.

3. What actually worked? What solved it? Be specific — the command, the config change, the conceptual shift, whatever fixed it.

4. What would you tell someone hitting this cold? If you were writing a guide for someone encountering this for the first time, what's the one-sentence takeaway they need?

5. Who was the user? (Developer, data scientist, DevRel peer, etc. — this affects audience framing)

---

Output

Produce all of the following once the Q&A is complete.

1. TIL Format

A short-form "Today I Learned" version suitable for a quick post, thread, or newsletter item.

Title: [Working title with "TIL" framing]

Body: 2–3 sentences. Start with what didn't work, then the solution, then the takeaway. Keep it punchy.

Format fit: Micro-post, thread starter, or newsletter TIL section.

2. Full Context Format

A longer framework for a blog post or deep-dive content.