gsd-fast

Execute trivial coding tasks inline without subagents or planning files.

4|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/electroheadfx/efx-mux --skill gsd-fast-electroheadfx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-fast
Source: https://github.com/electroheadfx/efx-mux/tree/main/.codex/skills/gsd-fast
Command: npx skills add https://github.com/electroheadfx/efx-mux --skill gsd-fast-electroheadfx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes planning overhead for very small tasks that can be completed directly in one pass, helping you make quick edits without spinning up subagents or workflow artifacts.

Core Features & Use Cases

  • Inline execution: Handles trivial changes directly in the current context.
  • No subagent overhead: Avoids spawning agents for simple fixes, additions, or forgotten commits.
  • Fast-use cases: Best for typo fixes, small config updates, minor refactors, or other one-sentence tasks that can be finished quickly.

Quick Start

Use the gsd-fast skill to make this small change directly in the current context.

Frequently Asked Questions about gsd-fast

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make small code edits without spawning subagents or creating workflow files?

To make small code edits without subagents, execute trivial tasks inline within your current context. This avoids spawning workflow artifacts like PLAN.md, allowing you to directly apply one-step changes such as typo fixes or minor config updates instantly.

When should I use inline execution for trivial tasks instead of a full planning workflow?

Use inline execution for trivial tasks when handling one-sentence changes like small config updates, typo fixes, or forgotten commits. It is designed for one-step workflows that require direct execution and minimal coordination, rather than complex refactoring needing planning artifacts.

What is the best way to handle forgotten commits and minor config updates quickly?

The best way to handle forgotten commits and minor config updates is through direct inline execution. By avoiding subagent overhead and planning artifacts, you can complete these trivial one-step workflows quickly and directly in the current context.

Does inline execution for small edits generate a PLAN.md file?

No, inline execution for small edits does not generate a PLAN.md file. It explicitly avoids creating workflow artifacts unless an interactive response is needed, ensuring that trivial tasks like small additions or minor refactors are completed with zero planning overhead.

Can I use this inline execution approach for complex refactoring or multi-step tasks?

No, this inline execution approach is not designed for complex refactoring or multi-step tasks. It is strictly limited to trivial tasks, simple additions, and one-step workflows, requiring avoidance of planning artifacts and subagents to finish tiny edits instantly.