Use explicit frameworks to make gaps visible: empty cells and weak branches are often where the real risk hides. Choose the tool to match the question; never decorate a foregone conclusion.
When to Use
Strategy, prioritization, incidents, competitive moves, org problems, or any messy situation with multiple stakeholders and causes.
Workflow
Pick one primary frame (add a second only if it adds non-overlapping insight):
SWOT — internal Strengths/Weaknesses vs external Opportunities/Threats.
Root cause — 5 Whys for linear chains; Ishikawa (fishbone) when many contributing factors cluster (people, process, tools, environment).
MECE — decompose the problem into buckets that are Mutually Exclusive and Collectively Exhaustive; sanity-check overlaps and omissions.
Populate honestly (including inconvenient items). End by stating the non-obvious insight the structure surfaced—what you would miss in free-form prose.
Examples
Example 1: Launch delay → fishbone across process/tools/people; often reveals dependency/integration rather than “lack of effort.”
Example 2: Vendor choice → SWOT + one Porter slice (supplier power + substitutes); highlights lock-in and switching costs beyond feature lists.
1---2name: structured-analysis3description: Structured Analysis4---5# Structured Analysis67Use explicit frameworks to **make gaps visible**: empty cells and weak branches are often where the real risk hides. Choose the tool to match the question; never decorate a foregone conclusion.89## When to Use10- Strategy, prioritization, incidents, competitive moves, org problems, or any messy situation with multiple stakeholders and causes.1112## Workflow13Pick **one primary** frame (add a second only if it adds non-overlapping insight):1415- **SWOT** — internal Strengths/Weaknesses vs external Opportunities/Threats.16- **Porter’s Five Forces** — industry/competitive pressure (rivals, entrants, substitutes, suppliers, buyers).17- **Root cause** — **5 Whys** for linear chains; **Ishikawa (fishbone)** when many contributing factors cluster (people, process, tools, environment).18- **MECE** — decompose the problem into buckets that are **Mutually Exclusive** and **Collectively Exhaustive**; sanity-check overlaps and omissions.1920Populate honestly (including inconvenient items). End by stating the **non-obvious insight** the structure surfaced—what you would miss in free-form prose.2122## Examples23**Example 1:** Launch delay → fishbone across process/tools/people; often reveals dependency/integration rather than “lack of effort.”2425**Example 2:** Vendor choice → SWOT + one Porter slice (supplier power + substitutes); highlights lock-in and switching costs beyond feature lists.
Run npx skillmds@latest add sethdford/structured-analysis in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Structured Analysis It is listed under Coding & Dev Tools on SkillMD.
This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
sethdford (@sethdford) published this skill. Their other Agent Skills are listed on their SkillMD profile.
sethdford