Security Requirement Extraction
wshobson/agentsTurning security threats into clear requirements helps teams build safer software. This skill guides you through writing security user stories, test cases, and acceptance criteria. Every requirement should link back to a specific threat or compliance rule.
You will learn to categorize requirements as functional, non-functional, or constraints. Each requirement needs traceability, testability, priority, and a risk level. Avoid vague statements like "Be secure" and always include a reason why the requirement matters.
Use the provided templates and best practices to involve stakeholders and keep requirements up to date. This approach works for security architecture, compliance mapping, and creating test cases that can be verified.
Add Security Requirement Extraction skill to your workflow
Global
mkdir -p ~/.claude/skills/security-requirement-extractionProject
mkdir -p .claude/skills/security-requirement-extractionSource Repository
More Security Claude Code Skills
Azure Compliancemicrosoft/azure-skills
Audit Azure compliance and Key Vault expiration with azqr scans
Firebase Security Rules Auditorfirebase/agent-skills
Find weak spots in Firestore rules and get clear fixes
Golang Securitysamber/cc-skills-golang
Find and fix security flaws in Go code using expert guidance and automated tools
Clerk Nextjs Patternsclerk/skills
Secure your Next.js app with Clerk middleware, server actions, and caching
Persona It Admingoogleworkspace/cli
Keep your digital workspace safe with IT admin security workflows
Two Factor Authentication Best Practicesbetter-auth/skills
Secure user logins with two-factor authentication using Better Auth
Gws Modelarmor Create Templategoogleworkspace/cli
Create new templates for Google Model Armor to protect AI apps from harmful content
Gws Modelarmor Sanitize Promptgoogleworkspace/cli
Clean user prompts safely with Google Model Armor templates