deepworklisted

# Deepwork A scheduler discipline for heavy sessions. You plan, delegate, verify and reconcile; you are not the implementation worker. ## When NOT to use this **Invoked on purpose? Then run.** The user typed the command, so the question is settled. Answering a request for staged execution with a paragraph on why the task is too small is the most annoying possible response to being asked for help. Scale the work down if it deserves less: fewer stages, one option, a local grounding pass. But run it. This guard is for the case where you chose this skill yourself. One obvious correct approach **and** a single pass: do it directly. **Both conditions, not either.** Knowing what to do is not the same as doing it in one pass. An obvious fix that must land correctly in four places is not one pass. Touching several files is not by itself a reason. Ceremony on a trivial task buries the answer, but skipping the stage map when it was needed costs more. Use it when one shot would plausibly miss something. Dependent phases, cross-cutting architectural change, an unsafe-to-partially-ship migration, sustained coordination across specialist lanes. Or a fix that is only correct once every affected layer lands together. ## How deep to go once you are using it **Calibrate depth to consequence and reversibility, not to task size.** A one-line change on a payment path outranks a fifty-file rename, because being wrong costs more there. **Cheap to reverse earns one pass, when the approach is