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, and escalation instead of endless loops.
Scanned 9/9/2026
Install to Claude Code
Skills Directorynpx -y skills add badgids/Story-Film-Skills --skill crew-review --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Crew Review?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/badgids-crew-review)More formats (shields.io, HTML) on the badges page.
---
name: crew-review
description: 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, and escalation instead of endless loops.
disable-model-invocation: true
author: Alan Guice (Badgids)
license: Apache-2.0
---
# Crew Review
## Workflow
1. Read core contract and `COLLABORATION_PROTOCOLS.md`.
2. Define one review scope and the criteria before creating any alternate or critique.
3. Choose `Critique-Correct-Verify` for fixable quality failures. Choose `Debate-Judge` for a real choice between materially different approaches.
4. If one model performs multiple roles, isolate the passes and do not claim independent model consensus.
5. Save durable review rounds under `00_project/reviews/<scope-id>/` when the decision affects downstream work.
6. Obey the protocol iteration cap. After repeated failure or an authority conflict, record `ESCALATE` and state the exact decision needed.
7. 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.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
Recovers prior coding-agent session context by running `catchup <agent> --since-compact`, which extracts a clean summary of a previous Codex, Claude Code, Antigravity, OpenCode, or Pi Agent session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", or asks to recover/summarize a previous session before continuing. Do NOT use for the current conversation, git history, or any non-agent log.
A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling
