prd-security-analysis

To add threat modeling to a PRD, the skill applies STRIDE methodology to authentication and payment features, identifying structured security threats. It delivers an augmented PRD chapter with specific security testing scenarios and sensitive data handling guidelines.

Ensuring privacy compliance for GDPR and CCPA involves mapping PRD requirements to relevant regulatory frameworks. The skill automatically generates compliance mappings, embedding data encryption recommendations and privacy guidelines directly into the product requirements document.

Yes, you can generate security testing scenarios by providing the PRD content or file path. The skill analyzes security-sensitive functions like APIs and user data handling, outputting structured testing scenarios and encryption recommendations.

Yes, this PRD security analysis supports API authentication and data encryption recommendations. It identifies sensitive information handling needs within the PRD and augments the document with structured security guidelines.

You need STRIDE threat modeling when a PRD involves security-sensitive features like login, payments, user data, or encryption. The analysis can auto-trigger during orchestration to harden product design before implementation begins.

To integrate security analysis chapters, provide the PRD content to trigger automatic augmentation during the dynamic enhancement phase. The skill auto-integrates with prd-orchestrator to append threat modeling, compliance mappings, and testing scenarios.