SuperAPI AI Directory

audit-escalation

Writing & research

View repository

Updated 10-28 08:38

About this skill

Audit Escalation

Determine whether pressure meaningfully intensifies across the sequence.

Escalation is valid when later beats change costs, options, relationships, interpretation, or reversibility—not merely size or noise.

Build the Pressure Map

For each beat record:

Beat Goal Pressure Escalation axis Cost Options lost/gained Reversibility Consequence

Audit Patterns

Flag:

  • repeated pressure with no changed decision
  • numerical/spectacle inflation only
  • stakes announced but never demonstrated
  • intermediate beat stronger than intended climax
  • escalation jump with missing connective rung
  • consequence reset after every beat
  • repeated threats against the same asset/person
  • irreversible consequences introduced too early
  • antagonist competence varying solely to preserve pacing
  • escalation that depends on characters behaving irrationally
  • no aftermath after a major irreversible turn

Findings

For every issue include:

  • Severity
  • Confidence
  • affected beats
  • exact escalation problem
  • why it weakens tension or credibility
  • smallest repair category

Repair categories:

  • add missing rung
  • change escalation axis
  • demonstrate consequence
  • reduce premature peak
  • preserve consequence
  • remove redundant beat
  • add reversal
  • add recovery/aftermath

Do not rewrite authored material by default.

Output

Overall escalation read

Pressure map

Strong escalation beats

Findings

Climax readiness

Recommended structural repairs

Final Quality Check

Ask: Do later beats force harder or more costly decisions, or are they simply louder versions of earlier beats?