Skip to content

Daily Workflow

This is the operator habit loop for gzkit-first GovZero parity.

Operating Contract

  1. OBPI is the unit of execution and completion.
  2. ADR is the roll-up boundary for attestation/audit lifecycle state.
  3. After planning an OBPI, execution should flow through the pipeline — either uv run gz obpi pipeline (CLI) or /gz-obpi-pipeline (skill). The CLI and generated hook surfaces share src/gzkit/pipeline_runtime.py as the canonical runtime engine.
  4. Run ADR closeout only when OBPI evidence is complete.

CLI vs Skill

Both surfaces invoke the same runtime engine. The difference is governance logic:

Surface What it adds
CLI (gz <verb>) Direct command execution — assumes governance steps already happened
Skill (/gz-<name>) Interview logic, forcing functions, staged orchestration, subagent dispatch

When a skill exists for your current workflow step, prefer it.

OBPI Increment Loop (Default)

  1. Orient
  2. CLI: uv run gz status + uv run gz adr status ADR-<X.Y.Z> --json
  3. Skill: /gz-adr-status ADR-<X.Y.Z>
  4. Execute through the pipeline
  5. CLI: uv run gz obpi pipeline OBPI-<X.Y.Z-NN>
  6. Skill: /gz-obpi-pipeline OBPI-<X.Y.Z-NN>
  7. Verify increment
  8. uv run gz obpi validate path/to/OBPI-<X.Y.Z-NN>-<slug>.md
  9. uv run gz implement --adr ADR-<X.Y.Z>
  10. uv run gz gates --gate 3 --adr ADR-<X.Y.Z> when docs changed
  11. Present evidence
  12. value narrative, key proof, verification outputs
  13. Run guarded sync
  14. CLI: uv run gz git-sync --apply --lint --test
  15. Skill: /git-sync
  16. Record OBPI completion from the synced state
  17. uv run gz obpi emit-receipt OBPI-<X.Y.Z-NN>-<slug> --event completed ...
  18. uv run gz obpi reconcile OBPI-<X.Y.Z-NN>-<slug>
  19. uv run gz adr status ADR-<X.Y.Z> --json
  20. Repeat for next OBPI

ADR Closeout Loop (When OBPI Batch Is Done)

  1. uv run gz obpi reconcile OBPI-<X.Y.Z-NN>-<slug>
  2. uv run gz adr audit-check ADR-<X.Y.Z>
  3. CLI: uv run gz closeout ADR-<X.Y.Z> / Skill: /gz-adr-closeout-ceremony ADR-<X.Y.Z>
  4. uv run gz attest ADR-<X.Y.Z> --status completed
  5. uv run gz audit ADR-<X.Y.Z>
  6. uv run gz adr emit-receipt ADR-<X.Y.Z> --event validated ...

Why This Order

  • It prevents hidden work-in-progress at ADR scope.
  • It keeps evidence close to each OBPI increment.
  • It preserves the verify -> ceremony -> guarded git sync -> completion accounting sequence from AirlineOps parity.
  • It preserves human attestation as explicit ADR-level authority.
  • It keeps audit/validation as post-attestation reconciliation.