agentleFS
yogsoth-aiyogsoth-ai/convergence/skills/counter-thesis-construction/SKILL.md

counter-thesis-construction

Skill2 starsChanged 6 months agoApache-2.0View on GitHub

Construct the strongest possible counter-argument to the convergence decision using Dialectical Inquiry and Thesis-Antithesis-Synthesis methods.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When the decision needs maximum intellectual rigor

    line 12
  2. Distinctive:

    When the problem domain is complex with legitimate competing views

    line 13
  3. Distinctive:

    When synthesis between thesis and antithesis might produce a superior option

    line 14
  4. Distinctive:

    When the decision will face external scrutiny

    line 15
  5. Distinctive:

    After debate, attempt synthesis — is there a superior option combining both?

    line 55

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Counter-Thesis Construction

Purpose: Build the most compelling counter-thesis to the convergence winner — not to overturn the decision, but to ensure it can withstand the strongest possible intellectual challenge and to surface any synthesis opportunities.

When to use:

  • When the decision needs maximum intellectual rigor
  • When the problem domain is complex with legitimate competing views
  • When synthesis between thesis and antithesis might produce a superior option
  • When the decision will face external scrutiny

Budget

MetricMinimum
Counter-thesis depthFull argument with evidence
Debate rounds>= 2 (thesis vs antithesis)
Synthesis attempts>= 1

State Ledger

thesis: <the convergence decision>
antithesis: <constructed counter-argument>
debate_rounds: []
synthesis_attempted: false
synthesis_result: null
final_verdict: null  # THESIS_STANDS | ANTITHESIS_WINS | SYNTHESIS_FOUND

Available Tactics

TacticWhen to Deploy
adversarial-debate-protocolDefault — formal advocate/critic/judge cycle
assumption-excavationWhen counter-thesis rests on different assumptions

Available SOPs

  • advocate-construction — build the counter-thesis case
  • critic-attack — attack from both thesis and antithesis sides
  • judge-verdict — render verdict on thesis vs antithesis
  • steel-manning-synthesis — attempt synthesis of thesis and antithesis

Execution Guidance

  1. Articulate the thesis (convergence decision) clearly
  2. Construct the strongest antithesis using advocate-construction
  3. Deploy adversarial-debate-protocol: thesis advocates vs antithesis advocates
  4. After debate, attempt synthesis — is there a superior option combining both?
  5. Judge renders final verdict with explicit reasoning

Output Format

strategy: counter-thesis-construction
thesis: <decision>
antithesis: <counter-argument>
antithesis_strength: <1-10>
debate_rounds: <count>
synthesis_found: true | false
synthesis: <if found>
verdict: THESIS_STANDS | ANTITHESIS_WINS | SYNTHESIS_FOUND
reasoning: <key evidence>
conditions: []

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.