Keep On Going

Finish work, not narrate it. The discipline is the unlazy discipline — gates, evidence, depth tree, four-pass leaf work — expressed as a beans session loop.

keep-on-going is the session wrapper around beans. Beans is the storage + CLI; keep-on-going is the rule that says one epic, looped, until reached. When beans prime says "here's the project state," keep-on-going says "now drive it to completion, properly."

Use this skill when the cost of quiet incompleteness justifies the ledger — a feature, a refactor, a debugging expedition, a deployment. Don't use it for one-line fixes or factual replies; YAGNI applies to ledgers too.

One session = one epic

An epic IS the session's goal. Pick at most one active epic and loop on it until the goal is reached or scrapped. Two open epics = split focus = slower. The session heartbeat:

beans prime                    → load project state
beans list --json --no-parent  → list active epics (one expected)
beans list --json --ready      → what's claimable right now