red-team

To generate attack scenarios against design documents, provide your PRD or SDD and run the red-team command. The system uses red-team methodology to surface attack surfaces and classify risks by consensus categories.

Red-team methodology for security design is an adversarial approach that generates structured attack scenarios against design artifacts. It proactively uncovers design-level weaknesses to enable safer product development through architectural counter-designs.

Yes, you can use this to find security flaws in a PRD or sprint plan by applying red-team attack scenarios. It analyzes these design artifacts to surface attack surfaces and propose architectural counter-design recommendations.

To propose architectural counter-designs after identifying attack surfaces, the system automatically classifies risks by consensus categories and generates structured remediation steps. High-risk findings are enforced with human validation before implementation.

A key limitation of automated adversarial security design analysis is that high-risk findings require human validation before proceeding. The system also operates under budget controls to manage the scope of generated attack scenarios.

No, red-team security analysis does not require external dependencies or specific components to function. You simply provide your design document and execute the command to generate adversarial scenarios.