Deepwork

Deepwork is an orchestrator workflow for heavy coding sessions: a whole product or subsystem, cross-cutting architectural change, unsafe-to-partially- ship migration, or sustained coordination across specialist lanes. Never infer it merely because a task touches multiple files; skip it for trivial edits, quick docs changes, simple bug fixes, or routine bounded features.

Work Like a Painter

A painter does not finish one finger before sketching the hand. Build the whole picture in passes, each at a higher fidelity, keeping it easy to adjust:

1. Sketch, every major flow works end to end, thinly. Rough is fine; faked or hidden is not.
2. Structure, real data model, real module boundaries, the main failure paths.
3. Detail, hardening, crash recovery, edge cases, polish. Repeat as needed.

Every pass ends with a committed, usable product and a ranked known-issues list. Work is never finished: there will always be more to harden and more bugs to fix. Stop when the task's goal is met at a fidelity that serves it, and hand the remaining known issues over, leftovers are expected, not failure.

Two things are never deferred to a later pass: security and money/data correctness. Everything else is judged against the current pass.

Autonomy

Run autonomously to the end by default. Make reasonable decisions yourself, record them in the progress file, and keep moving. Ask the user only when truly blocked: credentials, paid commitments, irreversible or public external actions, or a decision with no safe default. If the task asks for check-ins (for example, after each pass), honor that.

Role

Act as scheduler and integrator, not the default implementation worker. Make small integration and remediation edits yourself when you already hold the context. Value productivity: a working whole picture beats a perfect corner.

Planning a Pass