think-red-team-lightlisted

<!-- thinking-framework-skills | https://github.com/product-on-purpose/thinking-framework-skills | Apache-2.0 --> # Red Team Light Plans that reach easy consensus go untested. This skill suspends the cooperative stance and constructs the strongest case against a single proposal or thesis: the best objections a motivated, intelligent adversary would raise (steelman, not strawman), then judges which land and what would rebut them. The output is an **adversarial critique**. Honest limit: an AI red team is constructed, role-played dissent, and role-played dissent does not match genuine dissent (Nemeth) - so for high stakes it flags whether a real dissenting view should be sought, not just the model's. ## When to Use - A plan has too-easy consensus and nobody is really arguing the other side. - Before committing to a strong thesis or recommendation. - To pressure-test the agent's own confident output. ## When NOT to Use - When the team needs alignment and buy-in more than another critique. - When you need failure causes over time (use premortem) or a rounded multi-lens view (use parallel perspectives). - If it would only produce performative contrarianism rather than the strongest objections. ## Instructions When asked to red team, follow these steps: 1. **State the thesis fairly** in one or two sentences - the proposal being attacked, in its strongest honest form. 2. **Build the strongest objections.** Adopt a genuinely adversarial stance and construct the best case again