メニュー
Use when defining governance metrics, reading governance health snapshots, generating the governance dashboard, or understanding the governance data model. Referenced by the governance-auditor agent and the /governance-health command.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
This skill should be used when the user asks to "assess AI literacy", "run an assessment", "check literacy level", "evaluate our AI collaboration", "where are we on the framework", or wants to determine their team's AI literacy level using the ALCI instrument.
This skill should be used when an agent is deciding whether to author a dynamic workflow — a self-authored, ephemeral multi-agent harness — for a task. Use when the user asks about "dynamic workflows", "multi-agent harness", "fan-out", "subagents in parallel", "adversarial verification", "the ultracode trigger", "should I use a workflow", or when a task looks long-running, massively parallel, highly structured, or adversarial. Names the six composable patterns, the election rubric for when NOT to spend the extra compute, and the two governance invariants (INV-1 ephemeral-proposes, INV-2 quarantine).
This skill should be used when the user asks about "verification slots", "integrating a linter", "adding a deterministic tool", "harness-enforcer", "constraint enforcement interface", "wrapping a tool", or needs the technical reference for how deterministic and agent-based checks work in the harness framework.
Use when setting up automatic PR constraint enforcement via GitHub Actions — covers the advisory-vs-blocking split, workflow installation, configuration options, and reading the output
Use when the user wants to estimate or predict the cost, token usage, or time of a task BEFORE it runs — "how much will this feature cost to build", "estimate the tokens for this spec", "what will this slice cost", "predict the agent-compute time before I commit" — produces a token + time estimate as a range with disclosed confidence, adding a dollar figure only when an observability/costs snapshot grounds it. The prospective sibling of cost-tracking, which records actual spend after the fact.
Use when the user wants to capture AI tool costs, review spending trends, set cost budgets, or integrate cost data into health snapshots — guides quarterly cost capture, records data in a structured format, and updates MODEL_ROUTING.md with observed cost patterns
| name | governance-observability |
| description | Use when defining governance metrics, reading governance health snapshots, generating the governance dashboard, or understanding the governance data model. Referenced by the governance-auditor agent and the /governance-health command. |
Defines the metrics, snapshot formats, and dashboard specifications for governance health. This skill is referenced by:
governance-auditor agent when producing audit reports/governance-health command when displaying results/governance-audit command when updating snapshots| Metric | Type | Description |
|---|---|---|
| Total constraints | integer | Total governance constraints in HARNESS.md |
| Falsifiability ratio | percentage | Proportion of governance constraints scored as "falsifiable" |
| Falsifiable | integer | Number of constraints rated "Falsifiable" |
| Vague | integer | Number of constraints rated "Vague" |
| Semantic drift stage | integer (1-5) | Numeric semantic drift severity from the five-stage model |
| Drift velocity | enum (stable/increasing/decreasing) | Direction of drift trend between audits |
| Governance debt items | integer | Number of governance debt items identified |
| Aggregate debt score | integer | Sum of (severity x blast_radius) across all debt items |
| Frame alignment score | percentage | Proportion of governance constraints with confirmed three-frame alignment |
Governance metrics are expressed as a markdown section in audit reports. The governance-auditor includes a Governance Summary section that agents (including the snapshot generator) can parse directly:
## Governance Summary
- Total constraints: 4
- Falsifiable: 3 (with verification criteria)
- Vague: 0 (lacking operational meaning)
- Falsifiability ratio: 75%
- Semantic drift stage: 1/5
- Drift velocity: stable
- Governance debt items: 2
- Aggregate debt score: 8 (sum of severity x blast radius)
- Frame alignment score: 50%
| Metric | Fresh | Stale | Critical |
|---|---|---|---|
last_audit | < 90 days | 90-180 days | > 180 days |
drift_velocity | stable or decreasing | increasing for 1 quarter | increasing for 2+ quarters |
falsifiability_ratio | > 0.75 | 0.50-0.75 | < 0.50 |
debt_inventory_size | 0-2 items | 3-5 items | > 5 items |
Governance audit reports are written to
observability/governance/audit-YYYY-MM-DD.md by the
governance-auditor agent. Each report contains:
See references/dashboard-spec.md for the full HTML dashboard
specification — sections, data sources, visualisation types, and
colour schemes.
When governance data is aggregated across repos (via
/portfolio-assess), the portfolio dashboard gains: