← LeaderboardThe Skill Leaderboard

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.

Published by sickn33 ↗sickn33/agentic-awesome-skills

Try your first task

security-requirement-extraction

Start a fresh conversation. Replace the highlighted placeholders.

Use security-requirement-extraction to turn [threat model] and [business context] into actionable security requirements, user stories, acceptance criteria, and verification steps.

Required inputs

  • [threat model]
  • [business context]

User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗

SKILL.md

name: security-requirement-extractiondescription: "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."risk: safesource: communitydate_added: "2026-02-27"

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.