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 mvschwarz/openrig, a Coding project.
Related friction appears in 2 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: Summary A seat blocked on a runtime permission prompt is detected per-seat ( / ) but that signal never reaches anyone: the rig-level attention count ignores it and no watchdog policy can fire on it. In practice a Claude Code seat sat on a tool-approval prompt for 1.5 h in a 6-seat rig with an orchestrator and an…Excerpted from the public Issue. Read the complete thread before interpreting it.
Recruit: Recruit contributors who can replay the problem in a representative repository and development environment.
Guardrail: Use a fixed test case and compare completion, regressions and recovery against the unchanged baseline.
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.Use a fixed test case and compare completion, regressions and recovery against the unchanged baseline.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.