Better Planning · Comprehend (on-demand catch-up)

The quiet failure of agentic coding: the agents write more and more code, and you lose your grip on your own system — not all at once, but one unseen decision at a time, until you feel like a spectator to your own codebase. There's too much code to read it all, and the agents make calls you never see. This skill is the counter-move, and it works like a good colleague, not a scheduled review: when the human asks, explain the system plainly until they hold it again. Nothing to maintain, nothing to prove — comprehension on demand.

It carries the better-planning name because it's better with the family's artifacts — a TDD is a ready-made map, a drift ledger is a ready-made changelog — but it has no prerequisites: on a repo with no planning space at all, read the code and git history and explain from those. Never refuse a catch-up for lack of docs; a project with no design of record is where the human is most lost.

When it runs

Whenever the human wants their system back in their head: