Determine factors for backlog prioritization

[webchick]

Off the top of my head:

• Customer/partner request: Captured with label https://github.com/temporalio/ai-cookbook/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22customer%20or%20partner%20request%22
• Contributor accelerator: Captured with label https://github.com/temporalio/ai-cookbook/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22contributor%20accelerator%22

What else?

[webchick]

Discussing with @cdavisafc a bit today, here were some she noted:

• Customer signals: what's showing up in Gong calls, what are SAs talking about on Slack, what are recurring themes in support tickets.
• Community signals: what are we hearing at events, what are people talking about on Community Slack and across social media?
• Coverage expansion: does this add a new SDK language? (Vercel example) is this a non-mainstream frontier model? (Pydantic example)
• Household AI names: Gemini, OpenAI, Anthropic, etc. great to those names + "how to" info associated with Temporal.
• Fit: Is this a cookbook recipe? Or is it better as a tutorial, a Code Exchange example, a validated pattern, etc.
  • Note: Knowing this requires us first getting crisp on our definitions of what is what. ;)

[webchick]

Claude also suggests Ecosystem Signal — The single highest-leverage source is other framework cookbooks treated as a demand proxy — the LangChain/LangGraph cookbook, OpenAI cookbook, Anthropic cookbook, LlamaIndex examples, and the docs for CrewAI, AutoGen, and Pydantic AI. The reasoning: a pattern that all of them bother to document is one the market has already validated as worth documenting.