mcpField
S
security-requirement-extraction

security-requirement-extraction

github.com/sickn33Security48.7k244 installsUpdated today
Repository

About security-requirement-extraction

Security Requirement Extraction is a skill for turning threat analysis into actionable security requirements. It supports security stories, test cases, acceptance criteria, compliance mapping, and architecture documentation.

Key features

  1. 01Convert threat models into requirements
  2. 02Write security user stories
  3. 03Create security test cases
  4. 04Define security acceptance criteria
  5. 05Map compliance requirements

Use cases

  1. 01Turning threat analysis into requirements
  2. 02Writing stories for security features
  3. 03Defining security tests and acceptance conditions
  4. 04Organizing compliance requirement mappings

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sickn33/agentic-awesome-skills --skill security-requirement-extraction

After installing, type/security-requirement-extractionin Claude Code to confirm it loaded.

Bundled filesresources/implementation-playbook.md

Details

From the project README

Security Requirement Extraction

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.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Comments

Markdown supported