security-requirement-extraction

Derives security requirements, user stories, and test cases from threat models and compliance frameworks.

1|Updated May 10, 2026
One-click install
npx skills add https://github.com/Tgoldi/claude-skills --skill security-requirement-extraction-tgoldi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-requirement-extraction
Source: https://github.com/Tgoldi/claude-skills/tree/main/security-requirement-extraction
Command: npx skills add https://github.com/Tgoldi/claude-skills --skill security-requirement-extraction-tgoldi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Translating threat models into concrete, testable security requirements is slow and inconsistent, often leaving gaps between identified threats and implemented controls. This Skill converts STRIDE-based threat analysis into structured security requirements with acceptance criteria, test cases, and compliance mappings. ## Core Features & Use Cases - Threat-to-Requirement Extraction: Maps STRIDE threat categories (spoofing, tampering, repudiation, information disclosure, denial of service, elevation of privilege) to security domains and generates prioritized requirements with rationale and traceability. - Security User Stories & Test Cases: Generates user stories, epics, acceptance criteria, and security test specifications ready for agile backlogs. - Compliance Mapping: Maps requirements to PCI DSS, HIPAA, GDPR, and OWASP ASVS controls, producing traceability matrices and gap analyses. - Use Case: After completing a threat model for a payment API, feed the identified threats into this Skill to produce a full requirement set with priorities, test cases, and a PCI DSS compliance matrix. ## Quick Start Analyze the threats from my threat model and generate prioritized security requirements with acceptance criteria, test cases, and OWASP compliance mappings.

Frequently Asked Questions about security-requirement-extraction

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a threat model into security requirements?

Map each threat to its STRIDE category, then generate requirements using category-specific patterns tied to security domains like authentication or data protection. Each requirement gets a priority calculated from threat impact and likelihood, plus acceptance criteria and test cases.

How to write security user stories for agile teams?

Structure each story as 'As a [role], I want [security capability], so that [protection goal]' using domain-specific templates. Include acceptance criteria, a definition of done with security review steps, and traceability links back to threats and compliance controls.

Which compliance frameworks can security requirements map to?

The mapping templates cover PCI DSS, HIPAA, GDPR, and OWASP ASVS. Each security domain, such as authentication or audit logging, maps to specific control identifiers, enabling traceability matrices and gap analysis per framework.

How is security requirement priority calculated from threats?

Priority derives from multiplying numeric scores for threat impact and likelihood, each rated low through critical. Combined scores of 12 or more yield critical priority, 6 or more high, 3 or more medium, and lower scores map to low.

What are the limitations of automated threat-to-requirement mapping?

STRIDE-based pattern mapping produces generic requirement templates that need human refinement for system-specific context. Novel threats outside the six STRIDE categories and organization-specific compliance controls require manual requirement authoring.