Write the problem hypothesis
For [specific user], completing [job] is difficult because [missing capability], causing [measurable consequence].
You can name one user, one situation and one measurable consequence without proposing a feature.Evidence observed in VoltAgent/voltagent, a Research project.
Related friction appears in 3 independent repositories. This is stronger than one backlog item, but still requires direct user validation.
Project strength and demand confidence are measured separately.Reporter context: Is your feature request related to a problem? Please describe. VoltAgent's guardrail system validates content but doesn't deterministically authorize tool execution before it happens. With MCP servers proliferating, agents face silent injection risks where a poisoned prompt triggers unintended tool calls. The Open…Excerpted from the public Issue. Read the complete thread before interpreting it.
Recruit: Recruit people who can bring a recent literature, evidence-review or source-tracing task.
Guardrail: Measure citation accuracy, coverage and review time; never reward speed at the expense of source fidelity.
For [specific user], completing [job] is difficult because [missing capability], causing [measurable consequence].
You can name one user, one situation and one measurable consequence without proposing a feature.Deliver the outcome manually or with a narrow prototype before building a reusable feature.
A user completes the real workflow and commits time, data, distribution or budget to repeat it.Measure citation accuracy, coverage and review time; never reward speed at the expense of source fidelity.Information has value only when it changes action. This page turns one public signal into a bounded validation exercise. It is a research aid, not proof of demand, investment advice or a product recommendation.