breakdown
I don't want a conclusion yet. I want the ground laid out first, then the decisions separated out so I can make them, and only then your recommendation.
Three phases, in order, and phase 3 does not happen in this message.
Scope
If the user named a subject when invoking this skill, that is the subject. If they named nothing, the subject is whatever we are already working on — the thing you just proposed, the bug we are looking at, the decision in front of us. Don't restart the topic and don't ask me to restate it.
Before writing anything, gather the facts. Read the actual code, config, docs or data that the subject depends on. If a fact matters to the breakdown, verify it rather than recalling it, and delegate the sweep to a subagent when it means reading widely. A breakdown built on assumed facts is worse than no breakdown, because it looks complete.