메뉴
Post-draft check that every explicit question and sub-request in the task is answered in the response, in the form the task asked for — nothing dropped, deflected, or answered in the wrong shape.
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 | final-answer-completeness |
| description | Post-draft check that every explicit question and sub-request in the task is answered in the response, in the form the task asked for — nothing dropped, deflected, or answered in the wrong shape. |
| license | MIT |
Trigger (observable): The task contains more than one question or directive (multiple question marks, numbered questions, embedded format instructions), and a draft response exists and is about to be sent.
When NOT to activate: Single-question tasks whose draft visibly answers it; mid-drafting (run at send time, not while composing); the user rescoped the questions mid-session (latest instruction wins).
The corrected draft, plus (for 3+ question tasks) a one-line-per-question mapping showing where each is answered.
Known risk: Mapping tables appended to short answers, bloating a two-question reply. Mitigation: below 3 questions the check is silent — fix the draft, skip the table.
Max intended cost: ≤150 added output tokens beyond the answers themselves; one re-read of the task.
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 (partition the request into its parts and close each one) and in a documented reasoning-failure mode — confidence in a response outrunning the evidence that it actually covered the request. Sibling of an artifact-completeness check; this one covers the response text itself.
