Menu
Design test strategies, write test plans, and identify test scenarios for banking features
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
Perform STRIDE threat modeling during Sprint Planning for new features and APIs
Run UX review checklist for banking user flows, validate WCAG accessibility compliance, assess security UX patterns, and review customer interface design
| name | test-strategy |
| description | Design test strategies, write test plans, and identify test scenarios for banking features |
Invoke when planning test coverage for a new feature or reviewing test adequacy.
/ E2E \ ← Few: critical user journeys (login → transfer → verify)
/ Contract \ ← Medium: API contract validation against OpenAPI spec
/ Integration \ ← Medium: real DB (Testcontainers), real HTTP (WireMock)
/ Unit \ ← Many: business logic, validators, calculators
| Category | Line Coverage | Branch Coverage |
|---|---|---|
| Transaction logic | 95% | 95% |
| Authentication | 95% | 90% |
| API controllers | 80% | 80% |
| Utility classes | 80% | 70% |
| Configuration | 60% | N/A |