Credit Efficient Workflow

Original name

Original description

Use this for any non-trivial task — multi-step features, refactors, debugging investigations, research, or anything likely to span more than a couple of tool calls or a few back-and-forth turns. Front-loads scope and plan confirmation, keeps context lean, batches work, enforces tight output specs, and self-critiques before declaring done — all to cut wasted tokens/credits and avoid rework. Trigger this proactively at the start of substantial work, not only when the user explicitly asks to "save credits," "be efficient," or "watch usage.