revdiff-planning vs planning@cc-thingz: both hook ExitPlanMode, different feature sets — intended relationship?

[denysshnurenko]

I run both revdiff-planning@revdiff (0.3.8) and planning@umputun-cc-thingz (3.8.4). Both register a PreToolUse hook on ExitPlanMode, so both fire on every plan review.

Feature diff I found comparing the two launch-plan-review.sh / plan-review-hook.py pairs:

• revdiff-planning has rolling/compare-mode review — a <!-- previous revision: ... --> marker + snapshot chain, so round 2+ only shows the diff since the last round (--compare-old/--compare-new --collapsed).
• planning@cc-thingz has none of that (always --only, full plan every round), but has a native agterm branch (agtermctl session overlay open ... --block) and a $EDITOR fallback via plan-annotate.py, plus PLANNING_DISABLE_REVDIFF to bail out cleanly (useful for /remote-control).

Looks like planning might have forked/evolved from revdiff-planning and picked up agterm + editor-fallback along the way, but dropped rolling-diff. With both installed, Claude Code runs both hooks on every ExitPlanMode (per the hooks doc, PreToolUse verdicts merge as most-restrictive-wins) — so right now I get two review passes back to back, which is redundant.

Is coexistence intended, or should one supersede the other? If intended, is PLANNING_DISABLE_REVDIFF=1 (silencing planning's own review, letting revdiff-planning be the sole reviewer) the recommended way to combine them? If not — is rolling-diff missing from planning an oversight, or dropped on purpose?

[umputun]

running both isn't something I designed for. Both plugins hook ExitPlanMode, Claude Code runs each plugin's hook separately, so you get two passes. Pick one of them for plan review.

the history is the other way round from what it looks like. planning in cc-thingz had the ExitPlanMode hook first (Feb) and started routing to revdiff on 2026-04-04, revdiff-planning came a day later. Rolling compare-mode review was added later still, in #163, and only to revdiff-planning. So planning never had it, nothing was dropped.

PLANNING_DISABLE_REVDIFF=1 does silence planning's hook, with two costs worth knowing. The same var makes launch-plan-review.sh exit early, so the "Interactive review" option in /planning:make quietly does nothing and the flow reads that as "no annotations"; revdiff-planning can't fill the gap because /planning:make never calls ExitPlanMode. And the var is there for /remote-control, where the overlay opens on a host terminal the remote client can't see - revdiff-planning has no equivalent off switch, so setting it leaves that case unsolved.

one more thing about running both. If you review clean in the revdiff-planning pane but annotate in planning's, revdiff-planning drops its revision snapshots while the other plugin denies the call, so the next round has no baseline and falls back to the full plan.

rolling diff missing from planning isn't a decision, it just was never ported. If you want it there, open an issue in cc-thingz.

fixed the docs in #362 - README and the site said this plugin "does not conflict with other planning plugins", which was wrong for exactly your setup.