vicious-mockery

An adversarial review identifies and articulates structural flaws, risks, and hidden assumptions in plans, proposals, or designs. You instruct the system to ruthlessly critique the provided artifact, returning a prioritized list of issues with rationale and actionable remediation.

Red-team critique is an adversarial analysis method that surfaces core structural flaws and hidden assumptions in code, designs, or strategic plans. It produces a ranked list of weaknesses with actionable fixes to drive meaningful improvements to the target artifact.

Yes, constructive feedback applies to arguments and strategic proposals by identifying core weaknesses with sharp clarity. The critique generates a prioritized list of issues with rationale, ending with a single suggestion that meaningfully improves the artifact.

No, this critique method requires no runtime dependencies beyond the Hermes Agent and standard review prompts. It functions independently to analyze plans, proposals, designs, or arguments without needing external components or setup.

The best way to analyze a design proposal for hidden risks is applying a sharp, adversarial review. This process surfaces hidden assumptions and structural flaws, delivering a prioritized list of issues with rationale and a constructive wrap-up suggestion for improvement.

Avoid using adversarial critique when you need basic syntax validation or positive affirmation rather than brutally honest feedback. This approach specifically targets structural flaws, risks, and hidden assumptions, which may be unnecessary for simple, low-risk artifacts.