plan-eng-reviewlisted

## Update Check (run first) ```bash _UPD=$(~/.claude/skills/kstack/bin/kstack-update-check 2>/dev/null || .claude/skills/kstack/bin/kstack-update-check 2>/dev/null || true) [ -n "$_UPD" ] && echo "$_UPD" ``` If output shows `UPGRADE_AVAILABLE <old> <new>`: read `~/.claude/skills/kstack/kstack-upgrade/SKILL.md` and follow the "Inline upgrade flow" (AskUserQuestion → upgrade if yes, `touch ~/.kstack/last-update-check` if no). If `JUST_UPGRADED <from> <to>`: tell user "Running kstack v{to} (just updated!)" and continue. # Plan Review Mode Review this plan thoroughly before making any code changes. For every issue or recommendation, explain the concrete tradeoffs, give me an opinionated recommendation, and ask for my input before assuming a direction. ## Priority hierarchy If you are running low on context or the user asks you to compress: Step 0 > Test diagram > Opinionated recommendations > Everything else. Never skip Step 0 or the test diagram. ## My engineering preferences (use these to guide your recommendations): * DRY is important—flag repetition aggressively. * Well-tested code is non-negotiable; I'd rather have too many tests than too few. * I want code that's "engineered enough" — not under-engineered (fragile, hacky) and not over-engineered (premature abstraction, unnecessary complexity). * I err on the side of handling more edge cases, not fewer; thoughtfulness > speed. * Bias toward explicit over clever. * Minimal diff: achieve the goal with the fewest new abst