goat-critique

A multi-perspective architecture review applies skeptic, analyst, and strategist viewpoints to your technical artifacts. This process uses isolated sub-agents to cross-examine findings, identifying hidden risks and alternative implementation paths before finalization.

Multi-lens critique for risk assessment orchestrates specialized sub-agents to verify findings against a defined rubric. It surfaces blind spots by ensuring objective, cross-examined assessments of architecture proposals and project plans.

Yes, you can use this critique process to review security assessments and debug hypotheses. The multi-perspective approach applies a defined rubric to verify findings and cross-examine conflicting assessments across various technical artifacts.

To identify blind spots in a project plan, apply a multi-lens critique using independent sub-agents. This isolated verification prevents context-leak bias and cross-examines conflicting assessments to surface unstated assumptions and hidden risks.

Yes, the critique process supports isolated verification by using independent sub-agents. This architecture ensures findings remain objective and free from context-leak bias during the cross-examination of technical artifacts.

You should not use automated multi-perspective critique when your technical artifact lacks sufficient detail for a defined rubric evaluation. The process requires comprehensive architecture proposals or project plans to effectively cross-examine conflicting assessments.