gsd-fast

To fix a typo in a config file quickly, use a single command to execute the one-step task directly. This bypasses subagent spawning and planning overhead, executing straightforward tasks in under two minutes without generating plan files.

The best way to perform small refactoring is executing a direct one-step command for the specific change. This approach handles immediate, clearly defined actions by skipping subagent overhead and instantly applying the requested modification.

You need a single command for configuration changes when the modification is straightforward, clearly defined, and time-sensitive. It is designed for immediate one-sentence actions that do not require complex verification, research, or subagent spawning.

Yes, you can use this approach for quick command-line tasks if they can be fully described in one sentence and executed in under two minutes. It directly performs simple actions like fixing typos or adjusting settings without complex verification.

Subagent overhead occurs when a system defaults to generating planning files and spawning subagents for any task. This approach eliminates that overhead by directly executing simple, time-sensitive actions within a single command, avoiding unnecessary planning.

The limitation of one-step execution is that it only handles small, immediate actions fully describable in one sentence and completable in under two minutes. It is not suitable for tasks requiring complex verification, research, or multi-step planning.