Why does scope optimization fail?

The most common reason scope optimization fails: Narrowing scope so aggressively that the agent loses the capability it needs to accomplish its purpose. This is the inverse failure — under-scoping. A morning routine stripped to only coffee and calendar review may execute reliably, but if the workout and meditation were genuinely load-bearing for your productivity, removing them degrades the outcome. Scope optimization is not minimalism for its own sake. It is the removal of everything that does not serve the agent's mission, and the retention of everything that does. The test is functional: does the narrowed scope still achieve the intended outcome? If not, you cut too deep. Restore the element and find a different source of bloat.

The fix: Select one agent — a habit, routine, workflow, or recurring process — that currently feels bloated or unreliable. List every action this agent currently includes. For each action, classify it as core (directly serves the agent's primary purpose), supporting (indirectly useful but not essential), or migrated (belongs in a different agent or process). Remove all migrated items immediately. For supporting items, ask: does this item's presence make the core items less likely to execute? If yes, remove it. Rewrite the agent's scope as a single sentence: 'This agent does X.' If you cannot state the scope in one sentence, the scope is still too broad. Run the narrowed agent for one week and record completion rates and subjective effectiveness compared to the bloated version.

The underlying principle is straightforward: An agent that tries to do too much does nothing well. Optimize by narrowing scope to what matters.