constructive-thinking

# constructive-thinking Turn messy thinking into a leader-ready structure. The skill teaches a **method**, not a writing template — the method compresses chaos into a five-element brief: **Frame → Crux → Nodes → Tilt → Reasoning**. A senior leader does not have thirty minutes to absorb your story. They need you to put the structure on the table in three. This skill is the thinking discipline that makes that possible. --- ## When to Use Use this skill when the user is about to **output** something to an audience whose time is more valuable than their patience, and the raw material in their head is unstructured: - Briefing a senior leader on a technical decision or status - Pitching a proposal (RFC, ADR, project plan) and needs the one-page summary to land - Reporting up after an investigation (not the formal postmortem — the verbal brief) - Preparing slides or talk track for a presentation - Summarizing a long thread / Slack / email storm for someone who only has 3 minutes - Drafting an executive summary or TL;DR for any longer artifact - Cross-functional update where the audience does not share your context Trigger phrases observed in practice (CN + EN): > "向领导汇报", "整理思路", "做技术方案的 presentation", "做个 one-pager", "report up", "brief the boss", "summarize for leadership", "executive briefing", "TL;DR", "the main point" ## When NOT to Use Route to a different skill when: | Situation | Use this instead | |---|---| | Writing the **final polished document** (RFC, runbook,...