gsd-fast

Execute trivial code changes directly in the current context.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill handles very small development tasks immediately, so you do not need to spend time on planning, subagent coordination, or extra workflow files.

Core Features & Use Cases

  • Inline execution: Completes simple edits directly in the current context.
  • No planning overhead: Skips PLAN.md and other multi-step orchestration for tiny jobs.
  • Best for quick fixes: Use it for typo corrections, small config changes, forgotten commits, and one-off refactors.

Quick Start

Use the gsd-fast skill to fix the typo in the current file and apply the smallest safe change.

Frequently Asked Questions about gsd-fast

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

FAQPage Schema
How do I fix trivial code changes without generating extra planning files?

Fix trivial code changes by executing them directly in the current context without spawning subagents or creating plan files. This approach handles small refactors and typo fixes in a single pass with minimal overhead.

What is inline execution for quick fixes in software engineering?

Inline execution for quick fixes is a process that completes small edits directly in the current context. It applies to tiny code changes, typo fixes, and config edits that can be completed in under two minutes without multi-step planning.

When do I need to skip planning workflows for config changes and typo corrections?

Skip planning workflows for config changes and typo corrections when the task is a single-step update completable in under two minutes. Direct execution is intended for tiny jobs that require no multi-step orchestration or verification workflow.

Can I use gsd-fast for small refactors that require no subagent coordination?

Yes, you can use gsd-fast for small refactors that require no subagent coordination. It is designed for one-off refactors and trivial tasks, applying the smallest safe change directly without extra workflow files.

What is the best way to handle forgotten commits and one-off config edits?

The best way to handle forgotten commits and one-off config edits is inline execution within the current context. This method bypasses PLAN.md and other multi-step orchestration to apply single-step updates immediately.

What are the limitations of using a no-planning approach for code refactoring?

The limitations of a no-planning approach for code refactoring are that it only applies to trivial tasks completable in under two minutes. It does not support multi-step planning, subagent coordination, or verification workflows for larger updates.