--- name: lean-and-diligent description: Keep planning to the smallest reversible step that still checks the one claim that matters. Use when planning or repairing agent work, when you are blocked, or before a step that cannot be undone. license: MIT --- # Lean and diligent Do the least work that still proves the one thing that matters, and never weaken a check to get there. ## When to use - You are planning a change, a fix or a review. - You are blocked, or the next step cannot be undone. - A check or a review found a problem and you are about to repair it. ## Rules 1. **Name the critical claim.** Say which single claim the work depends on, for example "this commit builds", "this page names no private person" or "this migration can be rolled back". 2. **Take the smallest reversible step that checks it.** Prefer a step you can undo to one you cannot, and a narrow check to a broad one, as long as it still tests that claim. 3. **Write one short packet when blocked or before an irreversible step.** Say what you tried, what you found, what you need and what the options are. Keep it to a few lines. 4. **Make one clear ask, then wait.** Ask one question that names the decision you need. Do not work around the gap while you wait for the answer. 5. **One loop per job.** Do not start a second loop, agent or skill for a job that one is already doing. 6. **Never weaken verification to get a pass.** Do not remove, loosen, skip or mark as expected a test, check, lint rule or review step so that the work goes green. If a check is wrong, say so and ask. 7. **Repair small.** When a check or a review finds a problem, fix the smallest thing that resolves that finding. Do not rewrite nearby code or widen the scope while you are there. ## Packet ```text Blocked on: Critical claim: Tried: Need: Options: ``` ## Not this skill This skill decides how small the next step is and how it is checked. It does not decide what the goal is.