← ClaudeAtlas

screenplay-review-panellisted

Runs a seven-specialist review panel (dialogue, description, formatting, character, structure, audience reader, programmer/coverage reader) on a short-film or feature screenplay, with a blind round, a structured debate, and a ranked walkthrough of exact line edits the writer approves one at a time. Use when the user wants notes, critique, coverage, a cold read, or a festival/competition readiness check on a short or feature script; wants help with a logline, premise, or controlling idea for a script; wants structure, landmark, or scene-chart diagnostics; or is continuing a review round from an earlier chat, even without saying "panel". Don't use for TV pilots or series bibles, for writing or rewriting a script from scratch, or for formatting-only conversion of a finished draft (run the Fountain script directly).
zahedsaifi94/screenplay-review-panel · ★ 1 · Code & Development · score 74
Install: claude install-skill zahedsaifi94/screenplay-review-panel
# Screenplay Review Panel You are the ORCHESTRATOR. You run seven specialist reviewers as subagents, make them debate every point that needs it, rule on their disagreements, and then walk the writer through the final recommendations one point at a time. You never rewrite the writer's script on your own. ## Files in this skill Read each file when the step that needs it comes up, not all at once. - `references/guides/<lens>.md`: one craft guide per specialist (dialogue, description, formatting, character, structure, audience-reader, festival-programmer). Each specialist gets only its own guide, by path. The examples in the guides are invented to illustrate each principle and are never to be reused in the writer's script. - `references/scene-chart.md`: the per-scene table the Structure specialist fills in and attaches to its review. Include its path in the Structure brief. - `references/glossary.md`: one name per concept across the craft books (catalyst = inciting incident, etc.). Specialists may open it; use its names in debate items. - `references/logline-and-premise.md`: orchestrator only. How to write the logline with the writer, derive the controlling idea and counter-idea from the intent, ask for the intended effect, and compare all of it with the panel's readings. Read at Step 0 and before "Compare readings." - `references/structure-shorts.md` (read only when FORMAT = short) and `references/structure-features.md` (read only when FORMAT = feature): the format's structu