gsd-fast

Execute trivial one-step tasks inline without planning artifacts.

Updated May 22, 2026
One-click install
npx skills add https://github.com/yusaduymaz/loexai --skill gsd-fast-yusaduymaz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-fast
Source: https://github.com/yusaduymaz/loexai/tree/main/.codex/skills/gsd-fast
Command: npx skills add https://github.com/yusaduymaz/loexai --skill gsd-fast-yusaduymaz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes planning overhead for tiny, self-contained requests so simple changes can be completed immediately in the current context.

Core Features & Use Cases

  • Inline execution: Handles trivial tasks directly without spawning subagents or creating workflow artifacts.
  • Fast turnaround: Best for small fixes, quick refactors, simple additions, and forgotten commits that fit into one short response.
  • Low-friction interaction: Preserves user-question handling when clarification is needed, while keeping the workflow lightweight.

Quick Start

Tell the assistant to use $gsd-fast for a small task you want completed 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 trivial code changes without workflow planning overhead?

You can execute trivial code changes inline by skipping planning artifacts. This handles simple fixes, config changes, and small refactors directly in a single response without spawning subagents.

When should I use inline execution for small refactors?

Use inline execution for small refactors when the task fits in one short response. It is ideal for quick fixes, simple additions, and forgotten commits that require no PLAN.md files or workflow artifacts.

Can I complete config changes in a single response without creating files?

Yes, config changes can be completed in a single response without creating workflow artifacts. The task is handled directly inline, bypassing the need for subagents or PLAN.md files.

Does inline task execution still handle clarification questions?

Yes, inline task execution preserves user-question handling. If clarification is needed for a trivial task, it will pause to ask while keeping the overall workflow lightweight and low-friction.

What is the best way to handle one-step requests like forgotten commits?

The best way to handle one-step requests like forgotten commits is inline execution. It removes planning overhead, allowing small, self-contained requests to be completed immediately in the current context.