Requirements Analysis

Catches you when you start with "I want to build X" instead of understanding the actual problem. Works through five diagnostic states from no problem statement to validated requirements, asking pointed questions at each level: who suffers without this, what are real constraints versus assumptions, what's the walking skeleton version. The interventions are practical, like the jobs-to-be-done self-interview and constraint inventory templates. Honest about the solo developer trap of inventing imaginary users instead of facing your own needs. If you tend to jump straight to implementation or accumulate infinite backlogs, this forces the clarifying work before you write code. Hands off to system design once requirements are actually testable.