util-0-v2-handover

Please deep think / ultrathink as this is a complex task.

util-0-v2-handover

A conversation+code compaction handover that another LLM can paste in and resume immediately. V2 adds optional domain context so the receiving agent understands domain boundaries, ownership, and contracts.

CLI /util-0-v2-handover --plan "" # optional; used only for pointers/anchors --phase "" # optional; defaults to current/latest --format "compact|lean|json" # default: compact --max 1400 # token cap (default 1400; hard stop 1600) --domain "" # optional; scope handover to a specific domain

Hard Rules

Memory only: Do not open files or call tools. Summarize from session memory.

No scaffolding noise: No “Read…”, “Working…”, diffs, mermaid, stack traces, or step logs.

Pointers, not payloads: If a detail isn’t remembered, write ? and add a pointer in Refs (plan §/dossier/log).

Status tokens: [ ] pending, [~] in‑progress, [x] complete, [!] blocked.

Context protection: Obey strict caps; keep strings short (≤12 words) and lists Top‑N only.

Deterministic: Natural sort for IDs; consistent key order.

Entity preservation: File paths, function names, task IDs, decision IDs, and CLI commands MUST be preserved VERBATIM. Never paraphrase these — copy exactly or write “?”.

Two‑Stage Generation (single response)

Internal consolidation (silent): Think forward — what will the receiving agent need to DO next?

1. Ask: “What 5 questions will the next agent ask in their first 30 seconds?”
2. Recover: user’s explicit requests (quote key lines), decisions + rationale, code state, failed attempts, and blockers that answer those questions.
3. Identify ≤5 immutable facts and ≤3 verbatim user constraints for the anchors section.

Emit summary: Output one artifact in the requested format using the schema below. If near --max, drop lowest‑priority sections in the Trim Order.

Output Formats A) --format compact (default; tight and skimmable)

HOVR/2 microformat with short keys and capped lists. One fenced block; no extra text.

HOVR/2 m:{ts:"", plan:"<path or ?>", phase:"", feat:"<slug or ?>", prog:"<x/y or %>", domain:"<slug or ? — optional>"}

intent:{ primary:"", quotes:["", ...≤2], scope:["<in/out of scope>", ...≤3] }

timeline:{ just_completed:"<last task/action finished with ID>", current:"", last_actions:["", ...≤4] }

concepts:{keys:["<key concept [domain]>", ...≤6]}

code:{ files:["<abs path or ?>", ...≤8], hot:["@+n/-m or 'hot'>", ...≤6], domain_dirs:{"":"", ...≤6} }

decisions:{ adrs:[["ADR-####","", "affects ", "<domain — optional>", "<why ≤8w>"], ...≤4], other:[["","", "", "<why ≤8w>"], ...≤6] }

tasks:{ done:[ids…≤8], ip:[ids…≤5], pend:[ids…≤10], blk:[["",""], ...≤3], critdeps:[["T033","T032"], ...≤5] }

tests:{unit:"pass|fail|mixed|?", integ:"pass|fail|mixed|?", cov:"<%|?>", notes:"<≤80 chars>"}

risks:[["", "", "", "<domain — optional>"], ...≤5]

fails:[["","",""], ...≤4]

anchors:{ immutable:["", ...≤5], user_verbatim:["", ...≤3] }

next:{ task:"", tasks_file:"<absolute-path-to-tasks.md>", why:"", validate:["", ...≤3], cmd:"/the-flow 6 --phase "" --plan "" --task """ }

refs:{plan:" §<anchor|?>", tasks_file:"<absolute-path-to-tasks.md|?>", log:"<.../execution.log.md|?>", paths:["<key dir/file>", ...≤5]}

Trim Order (when hitting --max): code.hot → code.domain_dirs → fails → risks → concepts.keys → decisions.other → tasks.pend → code.files → tests.notes → refs.paths → anchors.immutable. Never trim: m, intent.primary, timeline.just_completed, timeline.current, next (including next.tasks_file), m.domain (when present), anchors.user_verbatim.