Perform STRIDE Threat Analysis

The skill applies systematic threat identification using the STRIDE methodology. It follows a fixed sequence: clarify the goals, constraints, and required inputs; apply relevant best practices and validate the outcome; and provide actionable steps with verification. When a request needs concrete patterns or worked examples of STRIDE-based threat analysis, it opens resources/implementation-playbook.md for the detailed version rather than improvising.

Use it when starting a new threat-modeling session, analyzing existing system architecture, reviewing security design decisions, creating threat documentation, training a team on threat identification, or preparing for a compliance audit. Do not use it for tasks unrelated to STRIDE analysis patterns, or when a different domain or tool is the better fit. It is not a substitute for environment-specific validation, testing, or expert review, and it stops to ask for clarification when required inputs, permissions, safety boundaries, or success criteria are missing.

Input is the system architecture or design under review and the specific reason for the analysis (new threat model, design review, documentation, training, or audit prep). Output is a STRIDE-based threat identification with actionable steps and verification, expanded into detailed patterns and worked examples via resources/implementation-playbook.md when the request calls for that depth.

Security engineers and architects who need to run or teach systematic threat modeling using STRIDE, whether for a new system design, an existing architecture review, or compliance and audit preparation.