critic-loop

Parallel peer review for academic manuscripts works by running four concurrent critics across evidence, method, argument, and expert perspectives simultaneously. This synchronized cycle identifies major issues in your draft, followed by an adjudication process that controls iterative improvements.

To run a critic loop on an academic manuscript draft, execute the /critic-loop command followed by your document path. This initiates the orchestration, running built-in pre-flight checks and render-based integrity tests before applying controlled edits to resolve major revision issues.

Yes, you can use a parallel critic workflow for thesis chapters, research articles, and academic reports. The orchestration targets any academic manuscript undergoing revision cycles, applying synchronized critiques and iterative adjudication to resolve major drafting issues.

The best way to resolve major manuscript revision issues is through iterative adjudication. After parallel critics surface issues from multiple perspectives, the orchestration applies controlled edits iteratively, ensuring the manuscript reaches a major-free state without duplicating work.

Yes, you need configured prompt templates and a fully rendered manuscript to run the critique loop. These inputs, combined with the orchestration, provide the structure required to execute pre-flight checks and process the concurrent critic evaluation cycle.

Avoid using a parallel critic workflow if your manuscript has not yet reached a rendered draft state, or if it requires minor copyediting rather than major structural or argumentative revisions. The orchestration is designed specifically to target and resolve major issues through iterative cycles.