requesting-red-team-review

Automate red-team scrutiny by dispatching a dedicated reviewer subagent that challenges conclusions before they are reported. The skill provides a standardized prompt template and categorizes issues by severity to guide corrective actions.

Trigger a red-team review after completing each analysis step and before writing up or reporting findings. This ensures critical evaluation is embedded in subagent-driven workflows and pre-registration processes.

A red-team reviewer subagent stress-tests results by applying adversarial questioning and structured evidence gathering. It records commit bounds (BASE_SHA and HEAD_SHA) and categorizes identified issues by severity.

Yes, you can integrate red-team critique into subagent-driven workflows to ensure critical evaluation is embedded in reporting and pre-registration. It uses a structured prompt set to guide adversarial questioning.

During a subagent red-team review, analysis issues are categorized by severity to guide corrective actions. The reviewer subagent uses a standardized prompt template to evaluate findings between commit bounds.

No specific dependencies are required to critique scientific conclusions with red-team review. It operates independently to dispatch a reviewer subagent and record commit bounds for tracking analyzed code changes.