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/session-end.md

View on GitHub
# Session end

You are here at the end of a phase or a session.

## At a phase boundary

Work top to bottom; the first that fits wins.

1. **Continue** — the next phase needs this one verbatim (design into booking,
   plan into the pipeline), or there is room left to think clearly.
2. **Clear** — nothing in this session matters to what comes next; the ledger
   and the handoff chain carry the state.
3. **Subagent** — a bounded, independent track that needs no steering,
   dispatched with its Why.
4. **Compact** — the context matters and you stay in the session; tell the
   summary what the next phase needs. `CLAUDE.md` § Compact Instructions lists
   what must survive.

Decide only at a boundary. Mid-phase, continue or split the rest into subagents.

## At the end of a session

1. **`gz-airlock`** — `uv run gz airlock out` accounts for what the transit
   disturbed.
2. **[Commit and sync](commit-and-sync.md)** — land the work.
3. **`gz-session-handoff`** — `uv run gz handoff create` writes the handoff:
   current state, decisions with their attribution, next steps, open loops.
   Use mode `CHECKPOINT` to bookmark mid-flight without concluding.

## Branches

- **Holding an OBPI lock** — the handoff must record the lock state; release
  the lock only through the pipeline's own path.
- **A ruling arrived after the handoff was written** — seat it in the next one
  with `--settled`.

## Only you can

Rule on the next session's advised steps when it resumes.

## Then

[Session start](session-start.md), next time.
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 CodeCodexUnverifiedInstall
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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated 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: 322kUpdated Claude CodeCodexVerifiedInstall