tvproductions/gzkit / .agents/skills/gz-how
gz-how
VerifiedUse when the operator asks "how do I …?" or "what can I …?", or when unsure which skill applies or two look alike.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.6 KB |
| references/adr-closeout.md | markdown | 1.2 KB |
| references/canon-content.md | markdown | 1.2 KB |
| references/codebase-upkeep.md | markdown | 1.1 KB |
| references/commit-and-sync.md | markdown | 1.0 KB |
| references/complexity.md | markdown | 1016 B |
| references/defects-and-ghis.md | markdown | 1.5 KB |
| references/does-it-work.md | markdown | 1.1 KB |
| references/idea-to-adr.md | markdown | 1.8 KB |
| references/looking-outward.md | markdown | 917 B |
| references/obpi-delivery.md | markdown | 1.9 KB |
| references/project-setup.md | markdown | 1.2 KB |
| references/release.md | markdown | 821 B |
| references/repair.md | markdown | 1.2 KB |
| references/session-end.md | markdown | 1.5 KB |
| references/session-start.md | markdown | 1.4 KB |
| references/skill-maintenance.md | markdown | 1.1 KB |
| references/surface-integrity.md | markdown | 1.1 KB |
| references/traceability.md | markdown | 849 B |
references/obpi-delivery.md
View on GitHub# OBPI delivery
The main path. You are here when an OBPI brief exists and the operator has chosen
to work it.
## Steps
1. **Plan.** Plan the OBPI, then **`gz-plan-audit`** checks the plan against the
ADR's intent and the brief's scope and writes the receipt the pipeline needs.
2. **`gz-obpi-pipeline`** runs five stages:
1. *Load context* — reads the brief and the plan-audit receipt, claims the
OBPI lock, writes the pipeline marker.
2. *Implement* — per task, an implementer subagent, then a spec-reviewer and
a quality-reviewer.
3. *Verify* — the quality checks, each wrapped by **`gz-arb`** so it leaves a
receipt.
4. *Present evidence* — the operator's gate.
5. *Sync* — `uv run gz obpi complete` records the attestation; the lock is
released.
3. **Along the way:**
- **`gz-obpi-brief-drift`** — before implementation and before completion,
check the brief still matches the project tree.
- **`gz-obpi-simplify`** — after implementation, review the OBPI's code for
reuse, quality and efficiency.
- **`gz-implement`** — Gate 2 for the parent ADR.
4. **`gz-obpi-sync`** — reconcile briefs and the ADR's table from the ledger.
## Branches
- **Already implemented** → `gz-obpi-pipeline` with `--from=verify`; **already
verified** → `--from=ceremony`.
- **A stage aborts** → the pipeline releases the lock and writes a handoff; the
next session resumes from it.
- **Another agent may be working nearby** → **`gz-obpi-lock`** to see or manage
claims. The pipeline claims its own lock.
- **A defect in this OBPI's own work** → fix it inside the pipeline and record
it in the brief; it is not a new issue.
## Only you can
Initiate the OBPI; nothing starts one on its own. Attest at Stage 4: your words,
relayed verbatim, are Gate 5 for every lane.
## Then
The next OBPI, or, when all of the ADR's OBPIs are complete,
[ADR closeout](adr-closeout.md).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |