Checking Simplicity

Use when the user asks to simplify, right-size, identify overengineering, compare with a stated smaller alternative, choose the smallest viable approach, check for simplicity as well, or test whether reuse removes the need for change on a named architecture, design, area, plan, technical choice, or code-level approach. General architecture comparison or product brainstorming without that simplification intent stays with planning. Also use during a build or plan-to-build handoff when the next step adds durable machinery the user's stated need does not name, including when the user did not ask to simplify. Completion of a brief or plan alone is not a trigger. Direct behavior-preserving cleanup of settled code stays with implementation. An unchanged subject with a clean result continues without another check.

jrgilbertson Updated
The Rookery banner showing Huginn returning with a field dispatch to a blueprint workspace

File contents

jrgilbertson/the-rookery commit 93f023f40d

Frequently asked questions

npx get-skill add jrgilbertson/checking-simplicity