メニュー
Audit a repo for ADR hoist debt and pre-trinity packages. Triggers on: adr gap, hoist debt, adr audit, pre-trinity packages, architecture drift.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | adr-gap |
| description | Audit a repo for ADR hoist debt and pre-trinity packages. Triggers on: adr gap, hoist debt, adr audit, pre-trinity packages, architecture drift. |
| argument-hint | [repo_root] [--create-beads] [--ci] [--allow-unknown] |
| tags | architecture, adr, audit |
| requires_standards | ["english-only"] |
Audit a repository for ADR hoist debt and pre-trinity packages.
Hoist debt occurs when an Architecture Decision Record's hoist_when condition becomes true —
meaning it's time to move a helper or pattern from a specific package into a shared location.
Pre-trinity packages are packages not yet covered by any ADR (not in any applies_to or
hoist_when.target list). These represent architecture drift — packages that predate the
Architecture Trinity decision framework.
--ci flag, to block on unresolved hoist debtThe skill runs adr-hoist-check.py against a repository root:
docs/adr/*.md and parses YAML frontmatterhoist_when block, evaluates the specified condition--create-beads)# Basic audit (report only, no side effects)
bash scripts/adr-gap.sh [repo_root]
# Create beads for all due hoists
bash scripts/adr-gap.sh [repo_root] --create-beads
# CI mode: exit non-zero if any hoists are due
bash scripts/adr-gap.sh [repo_root] --ci
# CI mode, allow unknown condition strings without failing
bash scripts/adr-gap.sh [repo_root] --ci --allow-unknown
Advanced: You can also invoke the Python script directly (useful when running from the plugin root where the canonical script path is accessible):
uv run scripts/adr-hoist-check.py <repo_root> [flags]
| Flag | Effect |
|---|---|
| (none) | Report only — list hoist debt and pre-trinity packages, exit 0 |
--create-beads | Create a bead (via bd create) for each due hoist (if no open bead exists) |
--ci | Exit non-zero if hoists are due, conditions are unknown, or frontmatter is malformed |
--allow-unknown | With --ci: do not exit non-zero for unknown condition strings |
ADRs use YAML frontmatter to declare hoist conditions. See references/adr-frontmatter.md
for the full specification.
Minimal example triggering a hoist check:
---
status: accepted
contract: id-taxonomy
applies_to: [pvs-x-isynet]
hoist_when:
condition: second_package_implements_contract
contract: id-taxonomy
target: adapter-common
trigger_bead_title: '[HOIST] makeIdHelper to adapter-common'
---
| Condition | Description |
|---|---|
second_package_implements_contract | True when any package beyond applies_to has declared this contract in its contracts.yml |
allowlist_entry_exists_for | Reserved for future use |
Packages declare their contracts via a contracts.yml marker file:
packages/
pvs-x-isynet/
contracts.yml # contains: [id-taxonomy, error-envelope]
pvs-charly/
contracts.yml # contains: [id-taxonomy]
adapter-common/
(no contracts.yml) # pre-trinity: no declared contracts
ADR Hoist Debt:
HOIST DUE: ADR-001-id-taxonomy.md
Condition: second_package_implements_contract
Bead: [HOIST] makeIdHelper to adapter-common
Evidence: pvs-charly
Pre-trinity packages:
adapter-common
enforcement_matrix_scanner.py from /project-context skillbd create and bd list for bead integration (requires bd CLI)references/adr-frontmatter.md for frontmatter schemaOrchestrate parallel implementation of multiple beads across cmux panes in dependency-aware waves. Use when implementing a whole feature area, dispatching multiple beads at once, or running parallel cld -b sessions. MUST USE when user says "wave", "parallel beads", "implement all beads for X", "start the beads", or references implementing more than 2 beads at once. Also triggers on "cmux dispatch", "multi-bead", "wave orchestrator".
Troubleshoot beads Dolt failures: `bd dolt` push/pull errors, merge conflicts, embedded/shared-server mode problems, remote auth issues, local DB recovery, re-clone, reflog restore, broken `.beads` Dolt config, and brew-services Dolt lifecycle. Use whenever beads sync or Dolt infrastructure is failing — symptoms like "beads do not sync", "cannot push issues", "no common ancestor", "not supported in embedded mode", "Dolt server unreachable", or "lost local database". Read the beads changelog first. Do not use for normal beads tracking (`bd create/ready/close`), standalone Dolt databases, or regular git push/pull.
Create and review agents (subagents). Use when creating specialized AI assistants, reviewing/auditing existing agents, deciding between agent vs skill vs command, or asking about agent best practices, multi-agent pipelines, and model selection. MUST BE USED when the user says "create agent", "new subagent", "review agent", "audit agent", "agent vs skill", or asks about multi-agent architecture.
Query per-bead token cost metrics from the local agent metrics database. Shows cost table, impl:review ratios, most expensive beads, cost trend over time. Triggers on: bead metrics, token cost report, bead costs, /bead-metrics.
Structured 4-stage retrospective for completed beads: Requirements vs Strategy, Strategy vs Execution, Iteration Review, Workflow Audit. Creates Trap/Pattern/Decision artifacts. Use when debriefing a bead, capturing session learnings, or running a compound retrospective.
Smart bead creation with type guidance, size routing, and auto-scenario generation for features. Use when creating beads, adding work items, or when user describes something to build/fix/improve. Triggers on bead erstellen, create bead, neues bead, new bead, bd create.