liquidware-ninjaSecond brain & toolkit
Personal project. Research and learning only. Not for production. No warranty.Not for production
  • Built on my own time for research and learning. Not affiliated with, endorsed by or supported by my employer, Liquidware or Microsoft.
  • Bring your own Liquidware licenses. Don't run any of it in production or against tenants and subscriptions that matter. Test in a dedicated lab first.
  • Provided "as is", without warranty of any kind, under each repository's license. You use it at your own risk and own the Azure charges it incurs.
  • Contributions and forks are welcome and encouraged on public repos. See Contribute.

0015. Take handoffs from other Claude projects as handoff issues

acceptedReviewed 2026-10-19Source: decisions/0015-family-format-handoff-issues.md

Context and Problem Statement

Work that starts in another of the owner's Claude projects, such as a family decision this KB has to adopt, used to arrive as a prompt the owner pasted by hand. The family now hands work over as an issue in the receiving repo. How does this repo receive handoffs and report back?

Considered Options

  • Take handoffs as handoff issues, as the family decided
  • Keep receiving pasted prompts

Decision Outcome

Chosen option: "Take handoffs as handoff issues", because the issue carries the whole ask, what it waits on and the report back, and the owner's approval stays one visible act: the handoff label.

Also recorded in: 2ndbrain, the source of truth for the issue's shape, approval, pickup and report back.

For this repo:

  • Installed from the family's template export: the handoff issue template, the scripts/kb/handoffs.py script, the SessionStart hook in .claude/settings.json that lists open handoff issues at the start of every session, the AGENTS.md line, and the handoff and handoff-proposed labels, which kb-freshness creates.
  • Only the owner makes a handoff live, by adding the handoff label. Claude never adds it.
  • A daily routine in the Liquidware Claude project lists this repo's open handoff issues, for days no session opens the repo. It comments once when a handoff is still waiting and stays quiet until that changes.
  • Report back: the receiving thread comments its PR links on the issue and closes it once the PRs are open. Merging stays the owner's.

Consequences

  • Good, because handoffs no longer depend on the owner pasting prompts and remembering what waits on what.
  • Bad, because the daily routine costs a run even on days with nothing to do.

More Information

First use: avd-liquidware#12, which adopted 0014 and this decision.

Linked from 2 pages