New to Claude Skills? Learn how to install them →

wshobson on GitHub

Security Requirement Extraction

Free

Transform threat analysis into actionable security requirements.

Get this skill

Free · Opens the source repo

What Security Requirement Extraction does

The Security Requirement Extraction skill is designed to assist developers and security professionals in translating threat models into concrete security requirements. By leveraging this skill, users can effectively convert identified threats into actionable items that guide the development of secure applications. It provides a structured approach to writing security user stories, creating security test cases, and documenting compliance requirements, ensuring that security considerations are integrated throughout the software development lifecycle.

This skill focuses on several core concepts, including requirement categories, types, and attributes. Users will learn to categorize requirements into business, security, and technical controls, ensuring a comprehensive understanding of how security fits into overall business objectives. The skill also covers different types of requirements, such as functional, non-functional, and constraints, providing clear examples to illustrate how each type can be articulated in a practical context.

Additionally, the skill emphasizes best practices for writing security requirements. It encourages users to trace requirements back to specific threats, ensuring that each requirement is relevant and actionable. By adhering to principles such as specificity, testability, and stakeholder involvement, users can create robust security requirements that can withstand scrutiny and evolve alongside changing threats. The included template library in references/details.md offers concrete examples and templates, making it easier to implement these concepts in real-world scenarios.

Overall, this skill is ideal for security architects, developers, and compliance professionals who need to ensure that security is a fundamental part of their development process. By utilizing this skill, teams can improve their security posture and create software that not only meets business needs but also protects against potential threats.

When to use it

Use this skill when you need to derive security requirements from threat models or when creating security user stories and test cases.

When not to use it

This skill may not be suitable for teams that are not focused on security or do not require detailed security requirements.

What you can build with it

Converting Threat Models

Use this skill to translate identified threats into specific security requirements that guide development.

Writing Security User Stories

Create actionable user stories that reflect security needs, ensuring they are integrated into the development process.

Mapping Compliance Requirements

Utilize the skill to align security requirements with compliance frameworks, making it easier to meet regulatory standards.

How to install Security Requirement Extraction

View source

1. Install with the skills CLI

npx skills add wshobson/agents/security-requirement-extraction --agent claude-code

2. Or install it manually

Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.

Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs

Inside SKILL.md

Written by wshobson

Security Requirement Extraction

Transform threat analysis into actionable security requirements.

When to Use This Skill

  • Converting threat models to requirements
  • Writing security user stories
  • Creating security test cases
  • Building security acceptance criteria
  • Compliance requirement mapping
  • Security architecture documentation

Core Concepts

1. Requirement Categories

Business Requirements → Security Requirements → Technical Controls
         ↓                       ↓                      ↓
  "Protect customer    "Encrypt PII at rest"   "AES-256 encryption
   data"                                        with KMS key rotation"

2. Security Requirement Types

TypeFocusExample
FunctionalWhat system must do"System must authenticate users"
Non-functionalHow system must perform"Authentication must complete in <2s"
ConstraintLimitations imposed"Must use approved crypto libraries"

3. Requirement Attributes

AttributeDescription
TraceabilityLinks to threats/compliance
TestabilityCan be verified
PriorityBusiness importance
Risk LevelImpact if not met

Templates and detailed worked examples

Full template library lives in references/details.md. Read that file when you need concrete templates for this skill.

Best Practices

Do's

  • Trace to threats - Every requirement should map to threats
  • Be specific - Vague requirements can't be tested
  • Include acceptance criteria - Define "done"
  • Consider compliance - Map to frameworks early
  • Review regularly - Requirements evolve with threats

Don'ts

  • Don't be generic - "Be secure" is not a requirement
  • Don't skip rationale - Explain why it matters
  • Don't ignore priorities - Not all requirements are equal
  • Don't forget testability - If you can't test it, you can't verify it
  • Don't work in isolation - Involve stakeholders

Frequently asked questions about Security Requirement Extraction

Similar skills