gsd-quick

Execute quick tasks with atomic commits and state tracking in STATE.md.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/onelee85/my-skills --skill gsd-quick-onelee85
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-quick
Source: https://github.com/onelee85/my-skills/tree/main/gsd-quick
Command: npx skills add https://github.com/onelee85/my-skills --skill gsd-quick-onelee85

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Execute quick tasks with GSD guarantees (atomic commits and state tracking) while skipping optional agents.

Core Features & Use Cases

  • Handles fast, deterministic task execution with optional research/planning gates and state updates
  • Spawns quick-mode planning and executors to produce auditable commits in STATE.md
  • Keeps contextual notes in CONTEXT.md and stores planning results under .planning/quick/

Quick Start

Mention gsd-quick and describe your task after it to run a quick, state-tracked execution.

Frequently Asked Questions about gsd-quick

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

FAQPage Schema
How do I automate ad-hoc task execution with atomic commits and state tracking?

The quick-workflow process handles fast, deterministic tasks by skipping optional agents and running quick-mode planning and executors. This approach produces auditable commits while maintaining state updates for minor code edits and lightweight maintenance.

How do I format code and record minor edits with guaranteed state tracking?

To format code and record minor edits with state tracking, execute the task using a quick-mode orchestration that automatically updates STATE.md and stores planning results under .planning/quick/. This ensures your lightweight maintenance is fully auditable.

Does the quick-mode workflow support research and full planning gates?

Yes, the quick execution workflow supports discuss, full, and research modes for optional research and planning gates. This allows you to satisfy gating and planning requirements even during fast task turnarounds.

What is the best way to execute fast deterministic tasks while skipping optional agents?

The best way to execute fast deterministic tasks while skipping optional agents is using a quick-workflow orchestration. It skips non-essential processes to provide quick turnarounds while still guaranteeing atomic commits and state tracking.

Where are planning results and contextual notes stored during quick task execution?

During quick task execution, planning results are stored under the .planning/quick/ directory, while contextual notes are kept in CONTEXT.md. State updates and atomic commit records are maintained in STATE.md.

When should I avoid using a quick-workflow for task execution?

You should avoid using a quick-workflow for task execution when tasks are not fast or deterministic, or when optional agents are required. It is designed specifically for lightweight maintenance, formatting, and minor code edits requiring quick turnarounds.