---
id: OBPI-0.0.48-05-skill-surface-sync
parent: ADR-0.0.48-gz-adr-pool-triage
item: 5
lane: Heavy
status: Draft
---

# OBPI-0.0.48-05-skill-surface-sync: **skill-surface-sync** — Add the canonical gz ADR pool triage skill, sync mirrors, and expose the operator invocation surface.

## ADR Item

- **Source ADR:** `docs/design/adr/foundation/ADR-0.0.48-gz-adr-pool-triage/ADR-0.0.48-gz-adr-pool-triage.md`
- **Checklist Item:** #5 - "OBPI-0.0.48-05: **skill-surface-sync** — Add the canonical gz ADR pool triage skill, sync mirrors, and expose the operator invocation surface."

**Status:** Draft

## Objective

**skill-surface-sync** — Add the canonical gz ADR pool triage skill, sync mirrors, and expose the operator invocation surface.

## Lane

**Heavy** - This OBPI changes a command/API/schema/runtime contract surface.

> Heavy is reserved for command/API/schema/runtime-contract changes. Process,
> documentation, and template-only work stays Lite unless it changes one of
> those external surfaces.

## Allowed Paths

<!-- What files/directories are IN SCOPE? Be explicit with paths. -->

- `.gzkit/skills/pool-triage/SKILL.md` — canonical skill body composing OBPI-01/02/03/04 deliverables; mirrors `ghi-triage` three-step structure with `pool-triage`-specific Step 1 prepass invocation
- `.gzkit/skills/pool-triage/scripts/triage.py` — bundled deterministic script (mirrors `.gzkit/skills/ghi-triage/scripts/` convention; the file may also live as `.py` under the skill dir per ghi-triage precedent — author wherever ghi-triage parallel lives)
- `src/gzkit/skills/pool-triage/SKILL.md` — wheel-shipping package copy (regenerated by `gz agent sync control-surfaces`; not hand-edited)
- `tests/test_pool_triage_skill_surface.py` — REQ-derived tests covering skill discovery, frontmatter validity, and mirror sync parity
- `docs/design/adr/foundation/ADR-0.0.48-gz-adr-pool-triage/obpis/OBPI-0.0.48-05-skill-surface-sync.md` — this brief (evidence updates only)

## Denied Paths

<!-- What files/directories are OUT OF SCOPE? Agents will not touch these. -->

- `.claude/skills/pool-triage/**` — vendor mirror; written by sync, never hand-edited (skill-surface-sync rule)
- `.github/skills/pool-triage/**` — vendor mirror; written by sync, never hand-edited
- `.agents/skills/pool-triage/**` — vendor mirror; written by sync, never hand-edited
- `src/gzkit/pool/**` — module surfaces are OBPI-01/02/03/04's territory (this OBPI imports them, does not edit)
- `docs/user/manpages/**` — manpage authoring is OBPI-0.0.48-06's surface
- Edits to upstream `.gzkit/skills/ghi-triage/SKILL.md` (precedent reference only; not modified)
- New runtime dependencies; CI files; lockfiles

## Requirements (FAIL-CLOSED)

<!-- Constraints that MUST hold. Numbered list. NEVER/ALWAYS language.
     These are the rules agents ground against. If not met, OBPI fails. -->

1. REQUIREMENT: `.gzkit/skills/pool-triage/SKILL.md` MUST declare frontmatter compliant with `SkillFrontmatter` (`name`, `persona`, `description`, `category`, `lifecycle_state`, `owner`, `last_reviewed`, `metadata.skill-version`, `model`) and MUST pass `gz validate --surfaces`.
2. REQUIREMENT: The skill body MUST encode the canonical three-step `ghi-triage` pattern adapted for the pool: Step 1 invokes the prepass composer (OBPI-01), Step 2 follows the cognitive-pass procedure (OBPI-02 governance doc included verbatim), Step 3 renders via the deterministic renderer (OBPI-03).
3. REQUIREMENT: The skill MUST expose two invocations — `/pool-triage` (full pool) and `/pool-triage --tags <theme>` (tag filter per ADR § Invocation surface).
4. REQUIREMENT: After hand-editing the canonical SKILL.md, `uv run gz agent sync control-surfaces` MUST be executed and `.claude/skills/pool-triage/SKILL.md`, `.github/skills/pool-triage/SKILL.md`, and `.agents/skills/pool-triage/SKILL.md` MUST appear byte-equivalent to canonical (mirror parity invariant).
5. NEVER: Edit `.claude/skills/`, `.github/skills/`, `.agents/skills/`, or `src/gzkit/skills/` directly — they are generated outputs (skill-surface-sync rule).
6. NEVER: Embed pool ADR cognitive judgment inline in the skill body; the structural-only rank-input contract (OBPI-02) is the deliverable.
7. ALWAYS: Bump `skill-version:` and `last_reviewed:` in the same edit per `.claude/rules/skill-surface-sync.md` non-negotiable rule #6.

> STOP-on-BLOCKERS: if prerequisites are missing, print a BLOCKERS list and halt.


## Creates these files

<!-- Net-new files this OBPI creates. Path existence is exempt for these entries per GHI #419. -->

- `.gzkit/skills/pool-triage/SKILL.md` **CREATE**
- `.gzkit/skills/pool-triage/scripts/triage.py` **CREATE**
- `src/gzkit/skills/pool-triage/SKILL.md` **CREATE**
- `tests/test_pool_triage_skill_surface.py` **CREATE**

## Discovery Checklist

<!-- What to read before implementation. Complete this checklist first.
     Order matters: read the structured input (parent ADR § Decision)
     before the unstructured one (allowed paths, prerequisites). -->

**Parent ADR (read first; order pinned — GHI #321):**

- [ ] **Parent ADR § Decision item — quote the line this OBPI implements** verbatim into the brief's Implementation Summary. The Decision item is the contract; everything else hangs off it.
- [ ] Parent ADR § Intent — the why-frame for the Decision read above.
- [ ] Parent ADR file: `docs/design/adr/foundation/ADR-0.0.48-gz-adr-pool-triage/ADR-0.0.48-gz-adr-pool-triage.md`

> **STOP:** If you cannot quote the parent ADR § Decision item that this OBPI implements, STOP and re-read. Do not proceed to Allowed Paths, Prerequisites, or implementation until the Decision quote is in hand.

**Governance (read once, cache):**

- [ ] `.github/discovery-index.json` - repo structure
- [ ] `AGENTS.md` or `CLAUDE.md` - agent operating contract

**Context:**

- [ ] Related OBPIs in same ADR

**Prerequisites (check existence, STOP if missing):**

- [ ] Required path exists or is intentionally created in this OBPI: `docs/design/adr/foundation/ADR-0.0.48-gz-adr-pool-triage/ADR-0.0.48-gz-adr-pool-triage.md`
- [ ] Required path exists or is intentionally created in this OBPI: `docs/design/adr/foundation/ADR-0.0.48-gz-adr-pool-triage/**`
- [ ] Parent ADR evidence artifacts referenced by this brief are present

**Existing Code (understand current state):**

- [ ] Existing tests adjacent to the Allowed Paths reviewed before implementation
- [ ] Parent ADR integration points reviewed for local conventions

## Quality Gates

<!-- Which gates apply and how to verify them. -->

### Gate 1: ADR

- [ ] Intent and scope recorded in this OBPI brief
- [ ] Parent ADR checklist item quoted

### Gate 2: TDD (Red-Green-Refactor)

- [ ] Tests derived from brief acceptance criteria, not from implementation
- [ ] Red-Green-Refactor cycle followed per behavior increment
- [ ] Tests pass: `uv run gz test`
- [ ] Validation commands recorded in evidence with real outputs

### Code Quality

- [ ] Lint clean: `uv run gz lint`
- [ ] Type check clean: `uv run gz typecheck`

<!-- Heavy lane only: -->
### Gate 3: Docs (Heavy only)

- [ ] Docs build: `uv run mkdocs build --strict`
- [ ] Relevant docs updated

### Gate 4: BDD (Heavy only)

- [ ] Acceptance scenarios pass: `uv run -m behave features/`

### Gate 5: Human (Heavy only)

- [ ] Human attestation recorded

## Verification

<!-- What commands verify this work? Use real repo commands, then paste the
     outputs into Evidence. These are CONSTRUCTION HOUSEKEEPING (lint, type,
     test, mkdocs) — they prove the codebase is healthy, not what the OBPI
     yielded. The yielded product belongs in the `## Demo` section below. -->

```bash
uv run gz validate --documents
uv run gz validate --surfaces
uv run gz lint
uv run gz typecheck
uv run gz arb step --name unittest -- uv run -m unittest -q tests.test_pool_triage_skill_surface

# OBPI-specific surface checks
test -f .gzkit/skills/pool-triage/SKILL.md
# expect pool-triage in the catalog
uv run gz skill list
uv run gz agent sync control-surfaces

# Mirror parity invariants (byte-equivalent after sync)
diff .gzkit/skills/pool-triage/SKILL.md src/gzkit/skills/pool-triage/SKILL.md
diff .gzkit/skills/pool-triage/SKILL.md .claude/skills/pool-triage/SKILL.md
```

## Demo

<!-- THE YIELDED PRODUCT, not housekeeping. Concrete, runnable invocations
     that demonstrate the capability this OBPI delivers — e.g. an actual
     diagnosis run against a real file, the `--json` form, an auto-chain
     trigger. The closeout ceremony walkthrough harvests this section
     (parser-validated; unregistered verbs are dropped). Prefer real paths
     and arguments over `<placeholder>` syntax. `--help` is not a demo. -->

```bash
# Invoke the skill (full-pool run)
# /pool-triage

# Invoke with tag filter
# /pool-triage --tags velocity

# Verify skill is discoverable via gz skill list
uv run gz skill list | grep '^pool-triage'

# Verify mirror sync produces byte-equivalent skill files across surfaces
md5 .gzkit/skills/pool-triage/SKILL.md .claude/skills/pool-triage/SKILL.md .github/skills/pool-triage/SKILL.md
```

## Acceptance Criteria

<!--
Specific, testable criteria for completion.
Each checkbox MUST carry a deterministic REQ ID:
REQ-<semver>-<obpi_item>-<criterion_index>
-->

- [ ] REQ-0.0.48-05-01: Given the canonical `.gzkit/skills/pool-triage/SKILL.md` exists, when `gz validate --surfaces` runs, then frontmatter validates against `SkillFrontmatter` and exit code is 0.
- [ ] REQ-0.0.48-05-02: Given the skill body, when read, then it includes Step 1 (prepass invocation), Step 2 (cognitive-pass procedure with Intent/Decision STOP pin), and Step 3 (deterministic-renderer invocation) in that order.
- [ ] REQ-0.0.48-05-03: Given the skill is registered, when `uv run gz skill list` is invoked, then `pool-triage` appears in the listing.
- [ ] REQ-0.0.48-05-04: Given `uv run gz agent sync control-surfaces` runs after a canonical edit, when sync completes, then `src/gzkit/skills/pool-triage/SKILL.md`, `.claude/skills/pool-triage/SKILL.md`, `.github/skills/pool-triage/SKILL.md`, and `.agents/skills/pool-triage/SKILL.md` are byte-equivalent to the canonical file.
- [ ] REQ-0.0.48-05-05: Given the skill body, when read, then it declares the `/pool-triage` and `/pool-triage --tags <theme>` invocations per ADR § Invocation surface.
- [ ] REQ-0.0.48-05-06: Given a `skill-version:` bump in the canonical SKILL.md, when committed, then `last_reviewed:` is also updated to today's date in the same edit (non-negotiable rule #6).

## Completion Checklist

<!-- Verify all gates before marking OBPI accepted. -->

- [ ] **Gate 1 (ADR):** Intent recorded in brief
- [ ] **Gate 2 (TDD):** RGR cycle followed, tests derived from brief, coverage maintained
- [ ] **Code Quality:** Lint, format, type checks clean
- [ ] **Value Narrative:** Problem-before vs capability-now is documented
- [ ] **Key Proof:** One concrete usage example is included
- [ ] **OBPI Acceptance:** Evidence recorded below

> For ceremony steps and lane-inheritance attestation rules, see `AGENTS.md` section `OBPI Acceptance Protocol`.

## Evidence

<!-- Record observations during/after implementation.
     Command outputs, file:line references, dates. -->

### Gate 1 (ADR)

- [ ] Intent and scope recorded

### Gate 2 (TDD — Red-Green-Refactor)

```text
# Paste test output here
```

### Code Quality

```text
# Paste lint/format/type check output here
```

### Gate 3 (Docs)

```text
# Paste docs-build output here when Gate 3 applies
```

### Gate 4 (BDD)

```text
# Paste behave output here when Gate 4 applies
```

### Gate 5 (Human)

```text
# Record attestation text here when required by parent lane
```

### Value Narrative

<!-- What problem existed before this OBPI, and what capability exists now? -->

### Key Proof

<!-- One concrete usage example, command, or before/after behavior. -->

### Implementation Summary

- Files created/modified:
- Tests added:
- Date completed:
- Attestation status:
- Defects noted:

## Tracked Defects

<!-- Record GitHub defect linkage when defects are discovered during this OBPI.
     Use one bullet per issue so status surfaces can preserve traceability. -->

_No defects tracked._

## Human Attestation

- Attestor: `<name>` when required, otherwise `n/a`
- Attestation: substantive attestation text or `n/a`
- Date: YYYY-MM-DD or `n/a`

---

**Date Completed:** -

**Evidence Hash:** -
