メニュー
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.
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.
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.
| name | final-report |
| description | 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. |
| model | claude-opus-4-8 |
| effort | high |
The final answer is the product. Lead with the answer, not the process.
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 output is
the only thing the user can safely act on, so carry verification, caveats, and
attestation labels forward.
RESULT: <answer, recommendation, or deliverable summary>
CHANGES: <files/artifacts changed or produced>
VERIFICATION: <checks passed, failed, skipped, gate types, with evidence>
IMPROVED BY FINAL GATE: <specific changes made after critique>
RISKS: <decision-changing assumptions, caveats, or unknowns>
NEXT: <only if human action is required>
For S2+ work, render VERIFICATION as a table so measured and judged checks are
distinguishable at a glance, with every attestation row flagged:
| check | gate_type | status | evidence |
|---|---|---|---|
| unit tests | command | passed | npm test exit 0 |
| metric reconciles to source of truth | command | passed | recon query diff = 0 |
| narrative reads clearly for the audience | attest (flagged) | passed | editor judgment |
A high attestation ratio on code/data work is a signal that the task was under-specified, not that it was thoroughly verified.