gsd-fast

Execute trivial tasks inline without subagents or planning overhead.

8|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/D0NMEGA/donnyclaude --skill gsd-fast-d0nmega
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-fast
Source: https://github.com/D0NMEGA/donnyclaude/tree/main/packages/skills/gsd-fast
Command: npx skills add https://github.com/D0NMEGA/donnyclaude --skill gsd-fast-d0nmega

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Execute small, self-contained tasks directly in the current context without spawning subagents or engaging in multi-step planning, eliminating overhead for tiny edits and tweaks.

Core Features & Use Cases

  • Inline task execution: perform quick edits or refinements in under two minutes without planning.
  • Zero-subagent workflow: avoids planning phase and PLAN.md generation for trivial changes.
  • Use case: fix a typo, tweak a config, or perform a small refactor that doesn't justify a full plan.

Quick Start

Fix a minor issue directly in the current file inline.

Frequently Asked Questions about gsd-fast

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

FAQPage Schema
How do I execute small config changes or typo fixes without triggering a full planning phase?

To execute small config changes or typo fixes without planning overhead, you can run an inline task workflow that skips PLAN.md generation and subagent spawning, applying edits directly in the current context for trivial modifications.

What is inline task execution for minor refactors?

Inline task execution for minor refactors is a workflow mechanism that performs quick edits directly in the current context without spawning subagents or generating multi-step plans, eliminating overhead for tiny tweaks.

Can I use this fast workflow to make small edits without generating a PLAN.md file?

Yes, you can use this fast workflow to make small edits without generating a PLAN.md file, as it explicitly avoids the planning phase and PLAN.md creation to execute self-contained micro-tasks directly.

When should I avoid using a zero-subagent workflow for code modifications?

You should avoid using a zero-subagent workflow for code modifications when the task is complex and requires multi-step planning, as this approach is strictly designed for trivial changes like typos, small config tweaks, and minor refactors.

What is the best way to handle forgotten commits and micro-tasks without incurring planning overhead?

The best way to handle forgotten commits and micro-tasks without planning overhead is to execute them inline using a fast workflow that bypasses subagent planning, directly applying the changes in the current context.