crew-review
Run bounded creative review using Critique-Correct-Verify or Debate-Judge for consequential story, screenplay, directing, storyboard, or shot decisions, with explicit criteria, persistent verdicts, an
SKILL.mdskills/crew-review/SKILL.md
GitHubCrew Review
Workflow
- Read core contract and
COLLABORATION_PROTOCOLS.md. - Define one review scope and the criteria before creating any alternate or critique.
- Choose
Critique-Correct-Verifyfor fixable quality failures. ChooseDebate-Judgefor a real choice between materially different approaches. - If one model performs multiple roles, isolate the passes and do not claim independent model consensus.
- Save durable review rounds under
00_project/reviews/<scope-id>/when the decision affects downstream work. - Obey the protocol iteration cap. After repeated failure or an authority conflict, record
ESCALATEand state the exact decision needed. - Apply accepted corrections through the owning specialist skill. A reviewer does not silently edit an approved upstream artifact.
Done
The scope has a PASS or an explicit escalated decision, the criteria and unresolved items are recorded, and the review did not exceed its bounded iteration count.