# Structured Analysis

> Structured Analysis

- Skill: `sethdford/structured-analysis` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add sethdford/structured-analysis`
- Raw SKILL.md: https://api.skillmd.com/api/skills/sethdford/structured-analysis/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: sethdford (https://skillmd.com/u/sethdford)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/sethdford/structured-analysis

---

# Structured Analysis

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.
- **Porter’s Five Forces** — industry/competitive pressure (rivals, entrants, substitutes, suppliers, buyers).
- **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.