Leanplan

Overview

Challenge whether a plan can achieve its stated outcome with the least justified complexity — then record what the user decided, without silently rewriting their document.

Core principle: prove the plan works before you cut it. A critic that only subtracts will eventually cut something the goal required. Outcome coverage comes first; complexity comes second.

When to Use

• A plan/spec/design exists and implementation hasn't started
• Someone suspects scope creep, speculative abstraction, or AI-slop scaffolding
• Before handing a plan to superbuild, writing-plans, or an implementing agent

Not for: reviewing a code diff (use /code-review), or creating a plan (use superplan).

Workflow