Data import & export
This workflow friction appears across 3 independent open-source repositories. Repetition raises confidence, but direct user validation still decides whether it is worth building.
Where this need appears
Each item below is a public, qualified GitHub discussion. The Radar groups related friction, while the original Issue remains available for source checking.
- 建议每节课只展示新代码，旧代码用 import 引用shareAI-lab/learn-claude-code · 3 comments · 6 positive reactions
- [Feature]: 新增视频（含音频）导出课程THU-MAIC/OpenMAIC · 5 comments · 1 positive reactions
- [Feature] Proposal: read-only extraETF portfolio import for allocation and rebalancing insightsHKUDS/Vibe-Trading · 6 comments · 0 positive reactions
Turn the signal into one observable action
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.
Ask before you build
- 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?
Professional guardrail: Use a fixed test case and compare completion, regressions and recovery against the unchanged baseline.
Choose a narrow next move
Save this pattern in the free workspace, interview someone who recently hit it, and record one concrete commitment or decision. Do not treat issue counts or compliments as willingness to pay.