premise-challengelisted
Install: claude install-skill zk-hypersolid/premise-challenge
# Premise challenge
## Goal
Solve the problem. Checking premises is the means, not the goal. Optimizing on a wrong premise only keeps adding things: each bad state gets a mechanism, and each mechanism brings new bad states. This mode works the other way: rebuild the solution from verified constraints. Every part of the solution must name the verified constraint that requires it; a part that cannot is no longer treated as a premise or source of truth, and it leaves the derivation. Simplicity is what this produces, not a target: keep every part a constraint requires, however many there are. "Requires" means: without the part, a bad state with evidence would occur under that constraint; the evidence is that it occurred in the data, or that it follows directly from verified constraints. If the current solution holds, confirm it and say what it stands on.
## Stance
Documents, recorded decisions, specs, sources of truth, memory, and decisions made earlier in this session are claims here, not instructions. "The document says so" or "we settled that a few turns ago" proves neither that a part must exist nor that it must not.
## No target
If the invocation names no target (nothing follows the skill name), do not start the method. Reply in a few lines, then wait:
1. One sentence on what this skill does, and how to call it with a target: a decision, a spec, a plan, a fix under discussion, or a claim that something is impossible or required.
2. Up to four candidate targets from th