gsd-fast

Execute trivial tasks inline without spawning subagents or planning.

264|11|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/rkz91/coco --skill gsd-fast-rkz91
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-fast
Source: https://github.com/rkz91/coco/tree/main/systems/gsd/skills/gsd-fast
Command: npx skills add https://github.com/rkz91/coco --skill gsd-fast-rkz91

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Execute a trivial task directly in the current context without spawning subagents or planning overhead.

Core Features & Use Cases

  • Inline execution: perform simple tasks without a planning phase.
  • Quick fixes: ideal for minor edits, typo corrections, or config tweaks.
  • Use Case: fix a small bug or tweak a config value in the current workspace and verify immediately.

Quick Start

Ask me to fix a tiny issue in the current context and I will execute it immediately without planning.

Frequently Asked Questions about gsd-fast

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

FAQPage Schema
How do I make a quick code edit without triggering planning overhead?

For minor config tweaks or typo corrections, use a fast inline workflow that completes tasks directly in the current workspace without spawning subagents or creating planning files.

What is the best way to fix a small bug in the current workspace immediately?

Quick fixes for minor edits or config values are executed directly in the current context, bypassing the planning phase entirely for immediate verification.

Can I perform inline execution for tasks that take under two minutes?

Yes, inline execution is designed for tiny edits, quick fixes, or minor config changes that can be completed in under two minutes without spawning subagents.

Does inline execution generate PLAN.md files for quick fixes?

No, the fast inline workflow does not generate PLAN.md files, ensuring trivial tasks are completed directly in the current context without planning overhead.

When should I avoid using a fast inline workflow for code changes?

Avoid using a fast inline workflow for code changes that require more than two minutes, complex planning, or spawning subagents, as it is strictly built for trivial inline tasks.