gsd-fast

Execute small edits and configuration changes directly without plan files.

1|Updated Sep 6, 2015

Search Tags:#bash #code refactor #inline execution #quick fixes #config changes #no planning

Ready to run

npx skills add https://github.com/deerawan/dotfiles --skill gsd-fast-deerawan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-fast
Source: https://github.com/deerawan/dotfiles/tree/main/claude/skills/gsd-fast
Command: npx skills add https://github.com/deerawan/dotfiles --skill gsd-fast-deerawan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the overhead of planning and subagents when the task is small enough to execute immediately, so you can move forward faster.

Core Features & Use Cases

One-sentence, inline execution: Handles tasks you can describe succinctly, without generating plan files or spawning subagents.
Fast fixes and small changes: Useful for typo fixes, config changes, small refactors, forgotten commits, and simple additions.
Clear boundary: Use it when the work can be done in under 2 minutes; use research/planning-heavy workflows for anything that needs verification or multi-step reasoning.

Quick Start

Describe the change you want and ask the gsd-fast skill to execute it inline right away.

Frequently Asked Questions about gsd-fast

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

FAQPage Schema

How do I execute quick code refactors without generating plan files?▼

Quick code refactors can be executed inline by describing the change directly. This approach skips planning overhead and subagent spawning, applying trivial edits like typo fixes and minor updates in a single pass.

What's the best way to make small config changes without spawning subagents?▼

Small config changes are best handled by running the edit inline within the current context. This allows simple configuration updates to complete end-to-end in under two minutes using basic shell tooling.

When should I use inline execution for bash tasks instead of a planning workflow?▼

Inline execution for bash tasks is ideal when the work can be finished in under two minutes. Use planning-heavy workflows for anything that needs multi-step verification, complex reasoning, or generating plan files.

Can I do one-sentence edits directly in my current context?▼

Yes, one-sentence edits can be executed directly in the current context. This handles simple additions and minor updates immediately without creating extra files or requiring subagent overhead.

Why does my quick fix workflow need to avoid generating PLAN.md files?▼

Quick fix workflows avoid generating PLAN.md files to eliminate unnecessary overhead. By relying on basic read, write, edit, and shell capabilities, small refactors complete instantly without spawning subagents.

Does inline execution work for complex multi-step code refactoring?▼

No, inline execution does not work for complex multi-step code refactoring. It is strictly designed for trivial tasks like typo fixes and simple additions that can be completed in under two minutes.