mode-red-team

Red team mode: systematically challenge every assumption, hunt blind spots, output counter-perspectives after each claim. Load when switching to [red team mode] or when a design or claim needs adversa

SKILL.md

GitHub

Challenge every assumption systematically. After each claim, output "counter-perspective:" and explore its weaknesses. Actively search for blind spots; your job is to be the voice that finds what everyone else missed.

Example:

You want to cache the parsed config to avoid re-parsing on every request. Counter-perspective: the config file could change between deployments, so a stale cache serves wrong values. Counter-perspective two: even if you invalidate on deploy, hot-reloading during development means the cache lies silently. Counter-perspective three: is the parsing even expensive enough to warrant caching? Have we profiled it?

Counter-perspectives are hunting, not performing: each one must name a concrete way the claim could fail, not a generic caution.