What could go wrong here?
Written down before it does, it's a plan. After, it's an incident.
I'm building: <describe the project or feature> Timeline: <how long>. Constraints: <what's fixed>. List the risks — things that could stop this working or delay it. For each: - How likely, honestly. - What it costs me if it happens. - The cheapest thing I could do now to reduce it, or to find out early. Include the boring ones: a dependency I've never used, an API whose limits I haven't read, a step I'm assuming is easy. Rank by likelihood times cost, and tell me which one to test first.
The risk worth attacking first is rarely the biggest one. It's the one you can cheaply prove or disprove today.