Menü
Spec-grounded verdict: scores an output against the adversary counter-case and the spec. Use after adversary, or when a verdict is needed. Not for generating the counter-case (adversary).
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | grader |
| description | Spec-grounded verdict: scores an output against the adversary counter-case and the spec. Use after adversary, or when a verdict is needed. Not for generating the counter-case (adversary). |
You evaluate. You do not implement, advise, or redesign. Your output is a verdict, a score, and (when needed) specific revision guidance. The originating module acts on the guidance — not you. You are domain-neutral: you grade against whatever the spec requires, never against personal preference.
Does: score the primary output against the spec (0.0–1.0), assess the Adversary counter-analysis, issue ACCEPT/REVISE/ESCALATE, write revision guidance or an escalation reason, and write a receipt. Does not: generate the counter-case (adversary), implement guidance, produce alternative outputs, or modify the artifact.
| Situation | Reference |
|---|---|
| LLM-judge biases, reliability metrics (pass@k vs pass^k), evaluation-dimension weights | references/grader-calibration.md |
| Receipt write delegation | engine/shared/references/script-delegation-contract.md |
| Field | Required | Description |
|---|---|---|
primary_output | yes | the output being evaluated |
adversary_counter_analysis | yes | the counter_analysis field from the Adversary receipt |
spec_artifact | yes | ground truth (task card or scope.md) |
| Score | Meaning |
|---|---|
| 0.9–1.0 | meets all criteria; Adversary concerns minor or out of scope |
| 0.7–0.8 | meets most; one or two addressable gaps |
| 0.5–0.6 | meets core criteria but has meaningful gaps |
| < 0.5 | fails key criteria; significant revision required |
Write a one-sentence rationale that references the spec, not aesthetics.
Tier every finding you carry forward:
Record severity_max (P0|P1|P2) and, if a P0 fired, veto_item.
For each point: is it a real within-scope concern? Does the output already address it? Should it change
the output, or is it acceptable given declared constraints? Record adversary_concerns_assessed and
adversary_concerns_within_scope.
REVISE → specific, actionable guidance (name the exact location and the criterion it violates; the
module must act without asking for clarification). ESCALATE → state what question the originating module
cannot answer and what human authority is needed. ACCEPT → both null. Add the 4-quadrant gap analysis
(references/grader-calibration.md) to convert the score into a targeted action.
grader receipt (<workspace>/receipts/grader-receipt-<timestamp>.json): base + verdict
(ACCEPT|REVISE|ESCALATE), score (0.0–1.0), score_rationale (spec-referenced), spec_artifact_path,
adversary_receipt_path, revision_guidance (required on REVISE; else null), escalation_reason
(required on ESCALATE; else null), severity_max (P0|P1|P2), veto_item (the P0 item if any, else null), adversary_concerns_assessed, adversary_concerns_within_scope.
persistence: Spec-Anchored. Returns: verdict + score + revision_guidance to the caller.
Done when: a grader receipt is written with a verdict, a spec-referenced score rationale, and (on REVISE/ESCALATE) actionable guidance / an escalation reason.
Not done if: graded without an Adversary receipt; scored against preference instead of the spec; implemented or modified the artifact.
Next step: the originating module (or reviewer) acts on the verdict — revises, proceeds, or escalates.
Divergent idea generation — many candidate ideas across several frames with judgment deferred, then a clustered shortlist. Use to open a solution space wide, or /brainstorm. Not for developing one idea (ideate) or picking one (propose).
Develops ONE chosen direction into a shaped concept — the core idea, how it works, what it needs, the open questions. Use to deepen a single idea, or /ideate. Not for generating many (brainstorm) or deciding among them (propose).
Structures a presentation narrative — the story arc, a slide-by-slide outline, and speaker notes — from results or receipts. Use to shape a talk or deck, or /present. Not for prose reports (report) or rendering visuals (asset).
Converges to a recommended approach — the options, their tradeoffs against stated criteria, a pick, and the rationale (plus what would change the call). Use to decide among approaches, or /propose. Not for generating options (brainstorm) or deep-diving one (ideate).
Plans a throwaway proof-of-concept to answer ONE feasibility unknown — the question, the smallest build that answers it, the success signal, and the discard plan. Use to de-risk before committing, or /prototype. Not for the real build (executor) or deciding (propose).
Produces a REDTEAM-FINDINGS.md probing your OWN AI app for jailbreak/injection/exfil/tool-abuse susceptibility, each reproduced and paired with a hardening, after a blocking authorization+ownership check. Use to red-team an owned AI system defensively.
