Try it
Add the skill to a bot, then ask your Chief of Staff:
“Use the Go Concurrency Patterns skill on this: [describe the job, or paste your notes].”
Explicitly state which category applies before recommending any code. Many problems belong to two categories simultaneously (e.g., fan-out with shared state collection requires both a worker pattern and protected aggregation).
What it covers
- Concurrency Classification
- Common Pitfalls to Avoid
- Recommended Pattern: Fan-Out with Per-Result Error Encapsulation