mystery-payoff-and-fairness-judge

name	mystery-payoff-and-fairness-judge
description	Use when evaluating mystery arcs, foreshadowing, twist fairness, chapter value, strategic intelligence, and whether a webserial meets the standard of earned escalation and inevitable payoffs.

Mystery Payoff And Fairness Judge

Use this skill to judge whether a chapter, arc, or outline actually earns the feeling of depth, danger, and revelation that mystery-heavy strategic serials promise.

Quick Start

• Read references/scorecard.md first.
• Use this after outlining, after drafting a chapter, or after a major reveal design pass.
• Pair with $strategic-webserial-architecture when the failure is structural rather than local.

Operating Loop

1. Identify the active promises and open questions.
2. List the visible clues, hidden clues, and misleading interpretations currently on the page.
3. Check causal integrity: what happened because of prior incentives, information, and capabilities?
4. Check intelligence integrity: who acted below their established level, and why?
5. Check chapter value: what changed in knowledge, pressure, alignment, cost, or danger?
6. Score the work using the rubric in references/scorecard.md.
7. Name the highest-level fix first: prose, scene, chapter, arc, or system repair.

Output Contract

Scope judged:
Promises in play:
Best working element:
Major failures:
Score summary:
Highest-level fix needed:
Revision order:
Residual risks:

Rules

• Findings come first. Do not soften major failures with vague praise.
• Do not reward obscurity. A fair mystery with tension beats a murky mystery with atmosphere.
• Do not call a twist "earned" unless the clues existed before the reveal.
• Do not excuse weak causality because the vibe is good.
• Separate local execution problems from architectural problems so the rewrite happens at the right level.