gsd-quick

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

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/GenproMM/MMLab_TOOLS --skill gsd-quick-genpromm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-quick
Source: https://github.com/GenproMM/MMLab_TOOLS/tree/main/.claude/skills/gsd-quick
Command: npx skills add https://github.com/GenproMM/MMLab_TOOLS --skill gsd-quick-genpromm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you execute small, ad-hoc tasks quickly while ensuring atomic commits and state tracking, without the need for research or discussion phases.

Core Features & Use Cases

  • Quick Task Execution: Handles small tasks with GSD guarantees (atomic commits, state tracking).
  • Quick Mode: Tasks are stored in .planning/quick/ and do not involve research, discussion, or plan-checking.
  • STATE.md Updates: Tracks completion of quick tasks in the "Quick Tasks Completed" table.
  • Use Case: Ideal for tasks where you know exactly what needs to be done, such as a quick code fix or an immediate update.

Quick Start

Run the gsd-quick skill with the specific task you want to execute.

Frequently Asked Questions about gsd-quick

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

FAQPage Schema
How do I execute quick code fixes with atomic commits and state tracking?

To execute small, ad-hoc tasks with atomic commits and state tracking, run the quick task skill directly with your specific instruction, bypassing all research and discussion phases.

What is the best way to handle ad-hoc tasks without triggering research or discussion phases?

The best way to handle ad-hoc tasks without research or discussion is to use a quick task execution mode, which stores tasks in a dedicated quick planning directory and skips plan-checking entirely.

How does state tracking work for small, immediate code updates?

State tracking for immediate code updates works by recording completed quick tasks in a dedicated STATE.md file, specifically within a 'Quick Tasks Completed' table to maintain project history.

Can I use quick task execution for complex updates requiring external research?

No, quick task execution is designed only for immediate, known tasks where you know exactly what needs to be done, and it explicitly skips external research and discussion phases.

Where are quick tasks stored when skipping the discussion and plan-checking process?

When skipping the discussion and plan-checking process, quick tasks are stored directly in the `.planning/quick/` directory to ensure fast execution and isolated state tracking.