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.建议每节课只展示新代码，旧代码用 import 引用
Evidence observed in shareAI-lab/learn-claude-code, a Coding project.
3 comments6 positive reactions98 days openProject Radar 95
enhancement
Start free validation sprint4 guided steps · private notes · cloud sync
SOURCE EVIDENCE
Read original GitHub Issue ↗Start with what users actually said
Reporter context: 现在每节课的 py 文件都把之前所有课的代码重新抄一遍，越往后文件越大。s01 才一百多行，到 s20 已经两千多行了。每次打开后面的课，一堆前面学过的代码堆在那里，要找本节课新加的内容得翻半天，看着头晕。建议把前面课的公共代码抽到一个文件里，后面开课直接用 import 引入就行，每节课的文件里只写这节课新教的那部分。这样文件短、重点清晰。Excerpted from the public Issue. Read the complete thread before interpreting it.
Interview five affected users
- When did you last need this?
- What outcome were you trying to reach?
- What did you use instead?
- How often does this occur?
- What commitment would prove it matters?
Run the smallest experiment
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.Make a build decision
- Build: repeated pain and active commitment
- Narrow: pain is real but the audience or job 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.