Security Requirement Extraction

Bridges the gap between threat modeling and actual implementation work. You feed it threat analysis or business context, and it generates concrete security requirements, user stories, or test cases you can hand to your team. Useful when you've identified threats but need to translate them into actionable dev tasks or compliance mappings. The skill includes an implementation playbook with patterns and examples, which matters because requirement extraction is where a lot of security programs stall out. It won't replace domain expertise or environment-specific validation, but it gives you a structured way to move from "here's what could go wrong" to "here's what we need to build."