gsd-fast

To execute quick config changes without planning files, you can use an inline workflow that processes one-sentence tasks directly, bypassing the creation of planning artifacts like PLAN.md for trivial fixes.

The best way to handle small code refactors under two minutes is inline execution, which directly applies the minor tweak in the current context without spawning subagents or adding planning overhead.

You should use inline execution instead of a full planning workflow when your coding task is trivial, can be described in a single sentence, and completed in under two minutes, such as fixing a typo or adjusting a config.

Yes, you can run a single-step task immediately without spawning subagents by requesting inline execution, which handles trivial tasks directly in the current context without subagent overhead.

Yes, inline task execution works for small refactors by directly applying changes in the current context, deliberately eliminating the generation of PLAN.md files and other planning artifacts.

The limitations of a no-planning workflow include its restriction to trivial tasks completable in under two minutes; complex coding tasks requiring multi-step planning or subagent spawning are not suitable for this inline approach.