37 lines
1.1 KiB
Markdown
37 lines
1.1 KiB
Markdown
---
|
|
name: security-requirement-extraction
|
|
description: "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: unknown
|
|
source: community
|
|
date_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.
|