Skip to content

tvproductions/gzkit / .agents/skills/gz-how

gz-how

Verified

Use when the operator asks "how do I …?" or "what can I …?", or when unsure which skill applies or two look alike.

references/adr-closeout.md

View on GitHub
# ADR closeout

You are here when every OBPI of an ADR is complete and the ADR itself is ready to
be witnessed.

## Steps

1. **`gz-adr-sync`** — discover `@covers` evidence, reconcile OBPI ledger state
   and register the ADR files.
2. **`gz-adr-status`** — confirm every OBPI shows complete and nothing blocks
   closeout.
3. **`gz-adr-closeout-ceremony`** — `uv run gz closeout <ADR-ID> --ceremony`
   walks the operator through the evidence and the ADR's fidelity assertions,
   then records the attestation and runs the closeout pipeline.
4. **`gz-adr-audit`** — the Gate 5 audit: verify the evidence and move the ADR
   from Completed to Validated.
5. **`gz-adr-emit-receipt`** — record a completed, validated or closed receipt
   event with its evidence, where the flow calls for one.

## Branches

- **An OBPI is still open** → back to [OBPI delivery](obpi-delivery.md).
- **The ADR changed a CLI, API, schema or runtime contract** (heavy lane) —
  docs (Gate 3) and BDD (Gate 4) must pass before the attestation.
- **A defect in accepted work surfaces here** → [Defects and GHIs](defects-and-ghis.md).

## Only you can

Attest the ADR. The ceremony presents; you witness and rule.

## Then

[Release](release.md).
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 323kUpdated Claude CodeCodexVerifiedInstall