revision-escalation

# /revision-escalation - 3-Strike Revision Control ## Purpose Prevent repeated local patches from making a draft or code path more inconsistent. Use this when the issue may no longer be wording or implementation detail, but specification, structure, evidence, or version-control drift. ## Trigger Words This skill activates on: `revision escalation`, `3-strike`, `three strikes`, `stop and diagnose`, `still wrong`, `still weird`, `unclear`, `weak`, `越改越乱`, `还是不对`, `还是怪`, `不够清楚`, `逻辑还是混乱`, `/revision-escalation`. ## Core Rule If the same issue remains unresolved after 3 revision attempts, treat it as a specification or structure problem before treating it as another local editing task. Do not make a fourth patch immediately. ## Revision Escalation Check Before editing again, classify the problem: | Category | Meaning | Next action | | --- | --- | --- | | Underspecified request | Target, constraint, audience, venue, or expected output is missing. | Ask for a concrete target before editing. | | Ambiguous feedback | Feedback is evaluative but not operational: "weird", "weak", "unclear", "not good enough". | Ask what should change. | | Local execution problem | The goal is clear, but the previous patch implemented it incorrectly. | Make one small targeted patch. | | Structural mismatch | The issue affects the research question, gap, contribution, evidence chain, section structure, module boundary, or venue framing. | Propose a restructure plan before editing. | | Evidence g...