メニュー
Before shipping, sweep for conditions that void the entire answer regardless of its quality — violated mandatory rules, missing required elements, forbidden resources, wrong output form. A hit is fixed, never caveated.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Check a deliverable against its actual consumer: who reads it, what they do next, what format and register they need, and what they will assert downstream on its basis. Activate when the deliverable has a named audience beyond the requester, or its text will be forwarded, announced, or acted on by someone absent from the conversation.
For any rule-like deliverable — code, regex, query, formula, validator, policy — enumerate the boundary inputs (empty, zero, one, max, duplicate, malformed, hostile) and actually exercise the most breakable three before shipping. Activate when the deliverable is executable or rule-like and will meet inputs the author didn't type.
State every claim at its actual evidence level — verified, inferred, assumed, guessed — and give credences only where an observable could score them; ban certainty language on unverified claims. Activate when a response makes claims about unobserved, future, or unverified state, or when the user asks how confident or likely something is.
Before intervening in a system, write the explicit causal chain from the proposed action to the intended outcome — every arrow marked verified or assumed — and check the weakest assumed arrow first. Activate when an intervention (fix, optimization, policy change, growth action) is proposed on a system whose mechanism has not been written down.
With multiple live hypotheses and a limited test budget, design the cheapest single test whose possible outcomes separate the hypotheses — with a results-to-verdict table committed before running anything. Activate when two or more competing hypotheses are on the table and the next step is choosing what test, experiment, or probe to run.
Enumerate every deliverable the request actually asked for and map each one to the work produced, so nothing asked-for is silently dropped, stubbed, or rounded up to done. Activate when a request contains multiple parts — an enumerated list, several 'and'/'also' clauses, or a spec with more than one required artifact — or before delivering a draft against such a request.
| name | disqualifier-scan |
| description | Before shipping, sweep for conditions that void the entire answer regardless of its quality — violated mandatory rules, missing required elements, forbidden resources, wrong output form. A hit is fixed, never caveated. |
| license | MIT |
Trigger (observable): The task defines pass/fail conditions, mandatory requirements, or a required format — or any deliverable is about to be declared finished against a spec, rubric, or submission rule set.
When NOT to activate: No external spec or rule set exists to disqualify against; early drafting where the structure is still moving; the same scan already ran on this draft version.
A disqualifier list with per-item check results (pass / HIT with quoted evidence / not-checkable), placed before the completion claim.
Known risk: Sweeping invented disqualifiers that the spec never stated, burning tokens on phantom rules. Mitigation: step 1 requires each item to trace to the task text.
Max intended cost: ≤250 added output tokens; re-read of the spec's requirement clauses.
Evidence status: EXPERIMENTALLY_TESTED — this repair content lifted a weak model on procedural tasks in controlled runs; the effect is task-concentrated, and automatic router selection of micro-skills is a separate, unproven layer.
Lineage: Grounded in an evidence-backed completion-integrity principle (a deliverable is not done while a voiding condition stands) and in a documented reasoning-failure mode — verifying surface form while missing the semantic requirements; applies the disqualifier-sweep pattern from the broader Piénsalo skill family.
