brse-structured-thinkinglisted

# BrSE Structured Thinking Use this skill to add logical structure to BrSE deliverables. It does not replace the domain skills (clarifier, impact-trace, client-report) — it is invoked when those outputs need a sharper structural pass. ## When To Use - A report has facts but the conclusion is hard to find. - A scope definition feels incomplete and you cannot tell what is missing. - A customer question is broad and needs to be broken into answerable pieces. - Ticket breakdown overlaps or leaves silent gaps. - A proposal, estimate, or process repeats "the usual way" without proving which constraints are real. - A problem statement is vague: "なんとなくおかしい" or "うまくいかない". ## When NOT To Use - The deliverable is already clearly structured — adding a framework is decoration. - The skill that produced the output already enforces structure — use that skill's gate, not a second pass here. - Time is too short and a rough structure already exists — ship and refine after. - The problem is missing facts, not structure — gather facts first; framework on top of unknowns produces a confident-looking guess. ## Cynefin Gate — Choose Approach Before Choosing Framework Before picking any framework, classify the situation. Frameworks below assume a **knowable** problem (Clear or Complicated). For **Complex** or **Chaotic** situations, frameworks alone produce a confident-looking but wrong answer. | Domain | Signal | Approach | What this skill offers | | ------ | ------ | -------- | -----------