chore: add source field to feature request issue template
Helps maintainers triage by requiring contributors to indicate where the idea originated (real use case, competitive reference, systematic gap, or external discussion).
This commit is contained in:
parent
252419e1f8
commit
5804a54898
|
|
@ -6,6 +6,17 @@ labels: enhancement
|
|||
assignees: ''
|
||||
---
|
||||
|
||||
## Source
|
||||
|
||||
**Where did this idea come from?** (Pick one — helps maintainers triage and prioritize.)
|
||||
|
||||
- [ ] **Real use case** — I'm using open-multi-agent and hit this limit. Describe the use case in "Problem" below.
|
||||
- [ ] **Competitive reference** — Another framework has this (LangChain, AutoGen, CrewAI, Mastra, XCLI, etc.). Please name or link it.
|
||||
- [ ] **Systematic gap** — A missing piece in the framework matrix (provider not supported, tool not covered, etc.).
|
||||
- [ ] **Discussion / inspiration** — Came up in a tweet, Reddit post, Discord, or AI conversation. Please link or paste the source if possible.
|
||||
|
||||
> **Maintainer note**: after triage, label with one of `community-feedback`, `source:competitive`, `source:analysis`, `source:owner` (multiple OK if the source is mixed — e.g. competitive analysis + user feedback).
|
||||
|
||||
## Problem
|
||||
|
||||
A clear description of the problem or limitation you're experiencing.
|
||||
|
|
|
|||
Loading…
Reference in New Issue