What problem does it solve? Academic and philosophical works often end badly: they either over-close by claiming to have explained the entire field, or under-close by simply stopping without completing their trajectory. This Skill evaluates whether an ending closes the work while keeping the conceptual field it mapped genuinely open. ## Core Features & Use Cases - Closure vs. Totalization Audit: Distinguishes legitimate closure (synthesis, return, reframing) from totalizing claims that the map has exhausted the territory. - Opening–Ending Relation Test: Checks whether the ending returns to, transforms, or abandons the initial question, and whether the final modality matches the evidence. - Structured Diagnostic Output: Classifies findings by severity (A–E), confidence, and recommendation, with explicit false-positive and false-negative guards. - Use Case: When reviewing the final chapter of a thesis on AI and knowledge production, use this Skill to verify the conclusion synthesizes the argument's trajectory without turning Node E into a hierarchical culmination or present capabilities into inevitable futures. ## Quick Start Analyze the final section of my manuscript and tell me whether the ending closes the work's trajectory without totalizing the field it opened.
