threat-model

# Threat Modeling Structured threat identification and risk assessment for software systems using STRIDE threat categorization and DREAD risk rating, producing both machine-readable Open Threat Model (OTM) JSON and human-readable markdown reports. ## Core Principles 1. **Risk-First**: Focus analysis effort on high-value assets and exposed trust boundaries. Not every component warrants equal analysis depth -- prioritize by data sensitivity and exposure. 2. **Evidence-Based**: Every identified threat must be backed by specific data flows, components, and trust zone crossings. A threat without a concrete scenario is speculation, not analysis. 3. **Repeatable**: The same project context must yield structurally consistent models regardless of which analyst or AI assistant performs the analysis. The three-phase workflow and verification checklist enforce this constraint. 4. **Dual-Output**: Always produce both OTM JSON (for toolchain integration) and a markdown report (for human review). Neither is a subset of the other -- both must be complete. 5. **Honest**: Explicitly state scope limits, assumptions, confidence levels, and what was NOT analyzed. A threat model that overstates its coverage is worse than one that honestly declares its boundaries. **A note on DREAD.** Microsoft deprecated DREAD in 2008 in favor of CVSS-based bug bar approaches. This skill retains DREAD for three reasons: (1) CVSS scores vulnerabilities, not threats -- DREAD ...