gsd-quick

Execute small development tasks with atomic commits and STATE.md tracking.

Updated May 15, 2026
One-click install
npx skills add https://github.com/Pear-Commerce/pear-ai-skills --skill gsd-quick-pear-commerce
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-quick
Source: https://github.com/Pear-Commerce/pear-ai-skills/tree/main/skills/gsd-quick
Command: npx skills add https://github.com/Pear-Commerce/pear-ai-skills --skill gsd-quick-pear-commerce

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the overhead of full GSD milestone workflows for small, well-defined ad-hoc tasks, letting you complete work quickly while still maintaining critical guarantees like atomic commits and STATE.md progress tracking.

Core Features & Use Cases

  • Lightweight GSD Execution: Runs the quick GSD workflow path for small tasks, storing work in .planning/quick/ separate from full milestone phases to avoid clutter.
  • Optional Quality Flags: Add --discuss to clarify ambiguous requirements upfront, --research to investigate implementation approaches before planning, or --full to enable plan checking and post-execution verification for higher quality guarantees.
  • Use Case: Ideal for fast, low-overhead work like small bug fixes or configuration tweaks where you already know the implementation steps, but still want commit hygiene and state tracking without full milestone ceremony.

Quick Start

Invoke the gsd-quick skill with a clear description of your small, well-defined task to execute it with GSD guarantees, skipping optional agents and full milestone overhead.

Frequently Asked Questions about gsd-quick

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

FAQPage Schema
How do I execute small development tasks with atomic commits and state tracking without full milestone overhead?

To execute small development tasks with atomic commits, you can use a lightweight workflow path that skips full milestone planning. This approach stores work in a separate directory and maintains commit hygiene and STATE.md progress tracking for low-complexity tasks.

What is a quick GSD workflow for software engineering tasks?

A quick GSD workflow is a lightweight execution path for well-defined, ad-hoc development tasks. It provides built-in state persistence and commit hygiene while avoiding the ceremony of full milestone workflows, making it ideal for small bug fixes or configuration tweaks.

Can I add clarification or research steps to ad-hoc task execution?

Yes, you can add clarification or research steps to ad-hoc task execution using optional flags. You can enable lightweight discussion to clarify ambiguous requirements upfront, or trigger investigation to research implementation approaches before planning.

When should I avoid lightweight task execution and use full milestone planning instead?

You should avoid lightweight task execution and use full milestone planning when tasks are complex, ambiguous, or require extensive research and discussion. The quick workflow is designed only for well-defined, low-complexity work where implementation steps are already known.

Does workflow automation store state separately for quick tasks and full milestones?

Yes, workflow automation stores state separately for quick tasks and full milestones. Quick task execution stores its work in a dedicated planning directory, keeping it isolated from full milestone phases to avoid clutter and maintain clear progress tracking.

How do I verify small bug fixes after running a quick task workflow?

To verify small bug fixes after running a quick task workflow, you can enable a specific verification flag. This adds post-execution verification and plan checking to the lightweight execution path, providing higher quality guarantees for your configuration tweaks.