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 HKUDS/nanobot, a Productivity project.
Related friction appears in 9 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: Bug Description Sudo only lasts for one turn, so the authorisation closes before the agent can do the command. Agent gets stuck in a loop trying to get sudo. Additionally, somehow when the agent reaches maximum iterations, it gets obsessed with the command it couldnt do. So even if you continue the conversation, the…Excerpted from the public Issue. Read the complete thread before interpreting it.
Recruit: Recruit people who repeat the task every week and can show their current calendar, notes or coordination workaround.
Guardrail: Measure repeated use and time returned across two cycles, not a one-time demo completion.
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 repeated use and time returned across two cycles, not a one-time demo completion.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.