メニュー
Standard verification gates for code, analytics, BI, writing, strategy, and documentation deliverables. Use before final delivery and inside review or test-runner subagents to record passed, failed, skipped, and not-applicable checks with evidence.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
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.
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.
| name | verification-matrix |
| description | Standard verification gates for code, analytics, BI, writing, strategy, and documentation deliverables. Use before final delivery and inside review or test-runner subagents to record passed, failed, skipped, and not-applicable checks with evidence. |
| model | claude-opus-4-8 |
| effort | high |
Verification is evidence, not confidence.
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 job is to
turn "looks good" into passed, failed, skipped, or attested checks with evidence.
Prefer command gates from gate-kit for mechanically checkable work. Use
attest only where no command/file/grep gate is realistic, and label those
checks as attestation in the final report.
check:
command_or_method:
gate_type: command | file_exists | grep | attest
status: passed | failed | skipped | not-applicable
summary:
evidence:
failure_details:
next_action:
Never hide unavailable checks. Mark them skipped and state the blocker.