Identify Pain Point
Domain: Package Ideation
🎯 Motivation
Before writing code, clearly articulate the problem you are solving. A sharp problem statement guides every design decision and helps you resist adding features that do not serve it.
📋 Concrete Example
Instead of “a better spreadsheet tool,” write: “Converting a .xlsx timetable to .ics calendar takes 20 manual steps. My package does it in one command.” The pain is specific and measurable.
🔗 Analogy
A doctor diagnoses the illness before prescribing medicine. If they just handed out random pills, most would be useless. Naming the pain precisely is the diagnosis step for your package.