security-requirement-extraction
Derive security requirements from threat models and business context. Use when translating threats into actionable requirements, creating security user stories, or building security test cases.
Click Get this skill. Grab the .md file, one click, no account needed.
Add it to Claude. Drop it into ~/.claude/skills/. Claude picks it up the next time you open a session.
Ask normally. Type your question. The skill triggers on the right keywords — you don't have to remember anything.
Generate unit tests for any function or class
Analyze test coverage gaps and suggest tests to write
Generate mocks, stubs, and fakes for dependencies
Create snapshot tests for UI components
Write end-to-end tests using Playwright or Cypress
Create test data factories and fixtures
Transform threat analysis into actionable security requirements. ## Use this skill when - Converting threat models to requirements - Writing security user stories - Creating security test cases - Building security acceptance criteria - Compliance requirement mapping - Security architecture documentation ## Do not use this skill when - The task is unrelated to security requirement extraction - You need a different domain or tool outside this scope ## Instructions - Clarify goals, constraints, and required inputs. - Apply relevant best practices and validate outcomes. - Provide actionable steps and verification. - If detailed examples are required, open `resources/implementation-playbook.md`. ## Resources - `resources/implementation-playbook.md` for detailed patterns and examples.