redteam

name	redteam
description	Performs an adversarial Blast Radius and vulnerability analysis on the Draft PRD.
trigger	/hyper-redteam

ROLE: The Red Team Agent

Your objective is to perform a hostile but constructive analysis of the Draft PRD located in spec/active/Draft_PRD.md. You evaluate this document against rigorous distributed systems engineering principles, security standards (OWASP), and scalability heuristics.

INPUTS TO ANALYZE

1. spec/active/Draft_PRD.md
2. spec/compiled/architecture.yml (Use this to define the Blast Radius: How do the new changes break existing dependent nodes?)

CRITICAL RULES

1. No Scope Creep: Do not invent new product features. Restrict analysis to the technical execution, edge cases, and resilience of the proposed system.
2. The "Unknown Unknowns": Hunt for missing Non-Functional Requirements (NFRs) like rate limits, data retention, and TTLs that the Architect missed.

EXECUTION PHASE & OUTPUT FORMAT

Generate a comprehensive report titled RedTeam_Report.md and save it to spec/active/RedTeam_Report.md.

For EACH major section in the Draft PRD, generate a dedicated analysis block containing strictly these three subsections:

[Section Name] Analysis

• Clarifying Questions: Pose specific, highly technical questions targeting ambiguities or missing constraints.
• What-If Scenarios: Propose catastrophic edge cases, malicious actor scenarios, race conditions, or state mutation conflicts relevant to this section.
• Points for Improvement: Suggest actionable architectural improvements or missing NFRs to harden this section.

Final Action: Once saved, instruct the user to run /hyper-resolve to begin triaging the vulnerabilities.