gsd-quick

Execute ad-hoc tasks with atomic commits and STATE.md tracking via quick workflow.

Updated Jan 28, 2025
One-click install
npx skills add https://github.com/aslaii/dotfiles --skill gsd-quick-aslaii
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-quick
Source: https://github.com/aslaii/dotfiles/tree/main/claude/skills/gsd-quick
Command: npx skills add https://github.com/aslaii/dotfiles --skill gsd-quick-aslaii

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ad-hoc tasks often lack atomicity and traceability. This skill enables executing quick tasks with GSD guarantees (atomic commits, STATE.md tracking) for predictable outcomes.

Core Features & Use Cases

  • Quick mode spawns gsd-planner and gsd-executor(s) for fast task execution
  • Quick tasks live in .planning/quick/ separate from planned phases
  • STATE.md updates with "Quick Tasks Completed" table (NOT ROADMAP.md)

Quick Start

Describe your task and let GSD execute it quickly with guaranteed commits and state tracking.

Frequently Asked Questions about gsd-quick

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

FAQPage Schema
How do I ensure atomic commits for ad-hoc tasks?

Atomic commits for ad-hoc tasks are guaranteed by isolating operations under .planning/quick and tracking progress in STATE.md via the GSD quick workflow.

What is the best way to track state for quick development tasks?

State tracking for quick tasks is handled by updating STATE.md with a Quick Tasks Completed table, avoiding ROADMAP.md to keep fast execution separate from planned phases.

How do I execute small tasks with planning and validation phases?

Small tasks are executed by spawning gsd-planner in quick mode and gsd-executor(s), enabling rapid execution with optional discuss, research, and validate phases.

Does the quick workflow support resuming interrupted ad-hoc tasks?

Yes, the quick workflow supports the resume subcommand, allowing you to continue interrupted ad-hoc tasks while maintaining state tracking and atomic commit guarantees.

When should I use a quick task workflow instead of planned execution?

Use the quick task workflow for small, ad-hoc tasks lacking atomicity and traceability, separating them from planned phases by storing task data in .planning/quick.