Write the problem hypothesis
For [type of user], completing [job] is difficult because [specific friction], causing [measurable cost].
You can describe one user, one job and one consequence without proposing a feature.知识库这里，希望支持文档的分类，添加，删除，批量导入文档
Evidence observed in zhayujie/CowAgent, a Agent Infrastructure project.
23 comments0 positive reactions115 days openProject Radar 95
enhancement
SOURCE EVIDENCE
Read original GitHub Issue ↗Start with what users actually said
Read the complete discussion before interpreting the problem. Note repeated use cases, workarounds, constraints and the people asking for the change.
Interview five affected users
- When did this last happen?
- What did you do instead?
- How often does it happen?
- What does the workaround cost?
- What have you already tried?
Run the smallest experiment
Deliver the outcome manually, with a script, template or narrow integration. Measure whether users return, share data or invest meaningful time.
A user completes the real workflow—not merely says the idea sounds useful.Make a build decision
- Build: repeated pain and active commitment
- Narrow: pain is real but the audience differs
- Stop: weak frequency or no behavioral proof
Why this brief exists
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.