Intellectual Honesty Enforcement

Detect handwaving by analyzing technical proposals for undefined steps, abstract frameworks, and hedge-word abuse. This Skill systematically identifies vague statements and forces authors to replace them with specific, testable claims and concrete justifications.

Enforce concrete commitments by requiring architectural documents to specify algorithms, quantify performance, and detail resource requirements. This Skill eliminates commitment avoidance by demanding concrete timelines and rigorous analysis of trade-offs.

Integrate counter-arguments by generating strong opposing viewpoints against technical proposals. This Skill constructs and integrates these counter-arguments to test the robustness of your positions and ensure rigorous, honest reasoning.

Identify knowledge gaps by distinguishing between known and unknown limitations in technical arguments. This Skill prevents redefining problems to fit available solutions, requiring honest acknowledgment of what remains unknown.

Evaluate trade-offs by enforcing rigorous analysis of competing technical positions within software engineering proposals. This Skill ensures authors detail specific justifications and testable claims rather than relying on vague terms.

Require specific testable claims whenever a technical proposal risks commitment avoidance or misrepresents knowledge gaps. This Skill ensures concrete positions are established, replacing undefined steps with rigorous analysis.