gsd-quick

Execute small tasks with atomic commits and state tracking.

Updated May 3, 2026
One-click install
npx skills add https://github.com/ThiagoVitale/endless-crystal --skill gsd-quick-thiagovitale
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-quick
Source: https://github.com/ThiagoVitale/endless-crystal/tree/main/.codex/skills/gsd-quick
Command: npx skills add https://github.com/ThiagoVitale/endless-crystal --skill gsd-quick-thiagovitale

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps streamline the execution of small, ad-hoc tasks while ensuring they are completed with guarantees such as atomic commits and state tracking.

Core Features & Use Cases

  • Quick Task Execution: Execute tasks efficiently without the need for extensive planning or validation.
  • Atomic Commits: Ensures that each task is committed atomically, preventing partial updates.
  • State Tracking: Tracks the state of each task, aiding in progress visibility and rollback if needed.
  • Skip Optional Agents: Saves time by not involving optional agents such as research, discussion, or verification stages.

Quick Start

Execute a quick task using $gsd-quick <task>.

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

Quick task execution with atomic commits is handled by running the task command directly, which processes the request while ensuring each update is committed atomically and state is tracked. It skips optional agents like research or verification to save time.

What's the best way to handle minor bug fixes without running optional validation agents?

Handling minor bug fixes without optional validation agents is possible by using a streamlined task execution mode that skips research, discussion, and verification stages. This approach focuses solely on atomic commits and state tracking for rapid completion.

When do I need atomic commits for small ad-hoc tasks?

Atomic commits for small ad-hoc tasks are needed when you want to prevent partial updates and ensure progress visibility. They allow you to track task state and roll back changes easily if something goes wrong during quick execution.

Can I skip research and discussion stages for streamlined task completion?

Skipping research and discussion stages for streamlined task completion is the core design of this quick execution mode. It avoids optional agents entirely, requiring minimal setup to execute tasks like minor updates or bug fixes efficiently.

Does quick task execution support rollback if a state tracking error occurs?

Quick task execution supports rollback through its state tracking feature. By tracking the state of each task and ensuring atomic commits, it prevents partial updates and aids in progress visibility, allowing you to revert if needed.

What are the limitations of skipping optional agents during task execution?

The limitation of skipping optional agents during task execution is the absence of research, discussion, and verification stages. This makes it unsuitable for complex tasks requiring extensive planning or validation, limiting its use to minor updates and bug fixes.