Stress-test a plan, brief or delivery claim against evidence and plausible failure modes. Use when the user asks for a red team or preparation for a consequential decision.
Start a fresh conversation. Replace the highlighted placeholders.
Use red-team to stress-test [the plan, brief, or delivery claim] against evidence and plausible failure modes. Provide the relevant context from [the .fde/ files or supplied artifacts] and identify what is being defended to receive a pre-blast challenge, an attack from five angles (Evidence, Stakeholder, Timeline, Dependency, and Second-order), and a final kill list of the most critical gaps.
Required inputs
[the plan, brief, or delivery claim]
[the .fde/ files or supplied artifacts]
User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗
SKILL.md
name: red-teamdescription: Stress-test a plan, brief or delivery claim against evidence and plausible failure modes. Use when the user asks for a red team or preparation for a consequential decision.
red-team
Purpose
A critique of weak claims, failure modes and corrective actions.
Load further references only when the task needs them. Everything linked is included in this skill; no other skill pack is required.
Principles
Work directly from the supplied permitted context. Standalone work does not require an engagement folder or initialization. Record filenames in the method are optional persistence destinations when no engagement is bound.
If called by @fde, reuse its current sanitized packet and scope. Do not restart setup, discovery or questions already answered.
The task context contract controls persistence and authority in both modes. Preserve unknowns and distinguish implementation, verification, deployment and acceptance.
Use the customer's repository instructions and available tools. Report a missing capability or unrun check honestly; do not claim that installing a skill provisions infrastructure.