gsd-quick

Execute ad-hoc tasks with atomic commits and state tracking in .planning/quick.

1|Updated Sep 6, 2015
One-click install
npx skills add https://github.com/deerawan/dotfiles --skill gsd-quick-deerawan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-quick
Source: https://github.com/deerawan/dotfiles/tree/main/claude/skills/gsd-quick
Command: npx skills add https://github.com/deerawan/dotfiles --skill gsd-quick-deerawan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you execute small, ad-hoc tasks with GSD guarantees while skipping unnecessary phases when you already know what to do.

Core Features & Use Cases

  • Atomic quick execution with state tracking: Creates a dedicated session under .planning/quick and updates STATE.md with a Quick Tasks Completed summary on completion.
  • Fast control of quality vs. speed: Defaults to skipping research, discussion, plan-checking, and verification, with flags to progressively add them back (including --full).
  • Session management for ongoing work: Supports listing tasks, checking status for a slug, and resuming an in-progress task by slug.

Quick Start

Ask the workflow to run a quick task by sending your task description to the gsd:quick run path (and add list/status/resume when you need to manage existing slugs).

Frequently Asked Questions about gsd-quick

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

FAQPage Schema
How do I run quick ad-hoc tasks with atomic commits and state tracking?

The workflow supports listing tasks, checking status for a sanitized session slug, and resuming in-progress work by passing the slug to the resume path, ensuring deterministic workflow selection for ongoing orchestration.

Can I skip research and validation phases for fast automation execution?

You can skip research and validation phases for fast automation execution by default, progressively adding quality gates back using flags like --discuss, --research, --validate, or --full when deeper checks are needed.

What is the best way to manage workflow orchestration for small, well-scoped automation?

No optional agents run unless explicitly requested, meaning the workflow skips discussion, research, plan-checking, and verification by default to prioritize speed for well-scoped tasks while maintaining atomic commits.

How do I resume an in-progress task by session slug?

You resume an in-progress task by providing its sanitized session slug stored in .planning/quick to the resume path, which restores the persistent state tracking and continues the workflow orchestration.