メニュー
Evidence, claim, assumption, and uncertainty ledger for high-rigor agent work. Use when synthesizing research, analytics, code review, strategy, or writing so important claims are labeled as verified, calculated, inferred, assumed, or unknown with source evidence.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | evidence-ledger |
| description | Evidence, claim, assumption, and uncertainty ledger for high-rigor agent work. Use when synthesizing research, analytics, code review, strategy, or writing so important claims are labeled as verified, calculated, inferred, assumed, or unknown with source evidence. |
| model | claude-opus-4-8 |
| effort | high |
Track the status of important claims before they enter the final answer.
This skill is part of ultracode-high. For the full orchestration map, tool
catalog, agent roster, and card schemas, read
../ultracode-high/references/runtime-context.md when available. Your ledger is
how the integrator separates facts from assumptions and decides what must be
relayed to the user.
VERIFIED: directly observed in a file, command output, source, test, or doc.CALCULATED: computed from inspected inputs with reproducible logic.INFERRED: best interpretation from evidence, not directly proven.ASSUMPTION: accepted default or user-provided premise not verified.UNKNOWN: material fact not resolved.claim:
label:
evidence:
source_path_or_method:
confidence:
decision_impact:
needs_relay_to_user: true | false
Surface high-impact assumptions and unknowns in the final answer.
Metric, SQL, dbt, dashboard, semantic-layer, and BI validation discipline for high-stakes analytics work. Use for grain, joins, nulls, filters, freshness, lineage, reconciliation, dashboard semantics, and decision relevance checks.
Compact task-state and handoff ledger for long Opus 4.8 High sessions, subagent orchestration, compaction, and resumable workflows. Use to preserve decisions, files, commands, evidence, risks, and next actions while dropping noisy logs.
Classify high-rigor work into S0-S4 scope levels and choose the minimal sufficient subagent set. Use for ultracode-high orchestration, complex coding, analytics, BI, strategy, writing, audits, migrations, and multi-domain tasks.
Final response contract for ultracode-high and high-rigor subagent workflows. Use to synthesize work into a relayable result with changes, verification, final-gate improvements, risks, and next actions.
Gate vocabulary and runner support for ultracode-high. Use to define precondition and completion gates, prefer deterministic command/file/grep gates where possible, flag attestation gates honestly, and run gates with the bundled gate_check.py helper.
Fork-style final gate for code and technical deliverables. Use after the draft result exists to check completeness, constraints, verification, risks, regression exposure, and final answer quality before handoff.