gsd-quick

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

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/ArtRiv/game-topicos-especiais --skill gsd-quick-artriv
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-quick
Source: https://github.com/ArtRiv/game-topicos-especiais/tree/main/.github/skills/gsd-quick
Command: npx skills add https://github.com/ArtRiv/game-topicos-especiais --skill gsd-quick-artriv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you complete small, ad-hoc work items quickly without skipping the core GSD guarantees like atomic commits and STATE.md tracking.

Core Features & Use Cases

  • Quick GSD execution: Runs the quick workflow end-to-end using gsd-planner (quick mode) plus gsd-executor(s).
  • Skip optional agents by default: Avoids research, discussion, plan-checking, and verification unless you explicitly request them.
  • State tracking for quick work: Records results in STATE.md under the “Quick Tasks Completed” table rather than ROADMAP.md.
  • Use case: When you already know exactly what needs doing (e.g., a straightforward refactor or a small documentation update), you can execute it immediately while still preserving commit safety and traceability.

Quick Start

Run a quick GSD task with atomic commits and STATE.md tracking for a well-specified small change.

Frequently Asked Questions about gsd-quick

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

FAQPage Schema
How do I automate small git tasks with atomic commits?

To automate small git tasks with atomic commits, you can use a quick workflow executor that runs end-to-end planning and execution while preserving commit safety and traceability in state tracking files. It skips optional agents by default to provide a fast execution path.

What is the best way to track state for ad-hoc documentation updates?

Tracking state for ad-hoc documentation updates is handled by recording results in a STATE.md file under a dedicated quick tasks table. This ensures work items are traceable without the overhead of updating a full project roadmap.

Can I skip research and verification steps for straightforward refactoring?

You can skip research, discussion, plan-checking, and verification steps for straightforward refactoring by using a quick workflow mode. This omits optional agents by default, allowing you to execute well-understood tasks immediately while maintaining commit safety.

How does workflow automation handle task execution for well-specified changes?

Workflow automation handles task execution for well-specified changes by applying a planner-executor model that preserves workflow gates. It routes already understood implementation tasks through a shorter workflow path to deliver fast results safely.

When should I avoid using a quick task execution path?

You should avoid using a quick task execution path if your work requires research, discussion, or verification. Because optional agents are omitted by default, this approach is not suited for complex implementation tasks that lack clear specifications.