Menu
Perform STRIDE threat modeling during Sprint Planning for new features and APIs
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Run chaos security engineering tests — AI agent attempts to hack the Sprint output and reports findings to the team
Validate Java and TypeScript code against banking naming conventions, style rules, quality standards, and secure coding practices
Perform OWASP Top 10 security assessments, vulnerability scanning, and PCI-DSS compliance checks
Design test strategies including security testing, write test plans, and identify test scenarios for banking features with DevSecOps integration
Run UX review checklist for banking user flows, validate WCAG accessibility compliance, assess security UX patterns, and review customer interface design
Design, review, and validate API contracts and OpenAPI specifications for banking services
| name | threat-modeling |
| description | Perform STRIDE threat modeling during Sprint Planning for new features and APIs |
Invoke during Sprint Planning when new features or APIs are being discussed.
# Threat Model: [Feature Name]
**Sprint:** [Sprint number]
**Date:** [YYYY-MM-DD]
**Participants:** [Security Champion + team members]
## Feature Description
[Brief description of the feature being threat-modeled]
## Data Flow Diagram
[Describe: User → Frontend → API Gateway → Service → Database]
## STRIDE Analysis
| # | Threat | Category | Likelihood | Impact | Risk | Mitigation | Story Points |
|---|--------|----------|-----------|--------|------|------------|-------------|
| 1 | [desc] | Spoofing | H/M/L | H/M/L | H/M/L | [control] | [pts] |
| 2 | [desc] | Tampering | H/M/L | H/M/L | H/M/L | [control] | [pts] |
## Security Stories Generated
- [ ] [Story title] — [priority] — [points]
## Residual Risks
- [Risks accepted with justification]