gsd-quick

Execute ad-hoc tasks with atomic commits and state tracking via subcommands.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly execute ad-hoc tasks with guaranteed atomic commits and persistent state tracking, reducing coordination overhead and ensuring reproducible results.

Core Features & Use Cases

  • Lightweight quick-task workflow that can initiate the planning and execution cycle with optional gates (discuss, research, validate) and maintain a transparent audit trail.
  • Supports subcommands list, status, resume, and run to manage quick-task lifecycles, monitor progress, and resume interrupted work.
  • Automatically updates and stores progress in planning directories and STATE.md to preserve an auditable history.

Quick Start

Provide a concise task description and run the quick workflow to execute it with default settings.

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 state tracking and atomic commits?

To automate ad-hoc task execution with state tracking, you can use a quick workflow pipeline that processes lightweight tasks, ensuring atomic commits and persistent state updates stored in planning directories and STATE.md.

What is the best way to manage quick task lifecycles and resume interrupted work?

Managing quick task lifecycles is done using subcommands like list, status, resume, and run, which monitor progress, execute isolated tasks, and resume interrupted work seamlessly.

How does state tracking work for lightweight planning and execution tasks?

State tracking for lightweight planning and execution works by automatically updating and storing progress in dedicated planning directories and a STATE.md file, preserving an auditable history across the task lifecycle.

Can I skip optional validation and research gates for quick task automation?

Yes, you can skip optional gates like discuss, research, and validate to rapidly execute isolated tasks while still maintaining the core GSD guarantees of atomic commits and transparent audit trails.

When do I need atomic commits for isolated software engineering tasks?

You need atomic commits for isolated tasks when you want to reduce coordination overhead and ensure reproducible results, guaranteeing that every state update across planning, execution, and history logs is persistent and auditable.

Why does my quick workflow pipeline require subcommands like run and status?

A quick workflow pipeline requires subcommands like run and status to manage task lifecycles effectively, allowing you to initiate execution, monitor current progress, and resume operations without losing context or state.