gsd-quick

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

Updated Aug 15, 2025
One-click install
npx skills add https://github.com/gesmith0606/nfl_data_engineering --skill gsd-quick-gesmith0606
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-quick
Source: https://github.com/gesmith0606/nfl_data_engineering/tree/main/.claude/skills/gsd-quick
Command: npx skills add https://github.com/gesmith0606/nfl_data_engineering --skill gsd-quick-gesmith0606

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gsd-quick provides a fast, opinionated workflow for executing small, ad-hoc repository tasks while guaranteeing atomic commits and persistent state tracking. It removes the overhead of a full planning pipeline when you already know the desired change, letting you safely perform focused edits and automations without skipping essential commit and state bookkeeping.

Core Features & Use Cases

  • Atomic commits & state tracking: Ensures changes are committed atomically and logged to STATE.md under the Quick Tasks Completed table.
  • Lightweight orchestration: Spawns a quick planner and executor pair and runs tasks in .planning/quick, skipping research and discussion by default.
  • Flag-driven quality controls: Supports --full to enable discussion/research/verification, --validate for plan-checking and post-run verification, and --discuss/--research for selective phases.
  • Use case: Ideal for small bug fixes, documentation updates, single-file improvements, or one-off automation scripts where speed and traceability are both required.

Quick Start

Use gsd-quick to execute a focused repository task, produce an atomic commit, and update the STATE.md "Quick Tasks Completed" table.

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

To execute quick repository tasks, the workflow spawns a planner and executor pair that performs focused edits, commits atomically, and logs changes to STATE.md under the .planning/quick directory.

What is the best way to automate single-file repository tasks without full planning overhead?

Automating single-file repository tasks without full planning overhead is achieved by using a lightweight orchestration workflow that skips research and discussion by default to safely perform focused edits with traceability.

Can I enable research and discussion phases for small documentation edits?

Yes, you can enable research and discussion phases for documentation edits by using the --full flag, or selectively apply --discuss and --research flags to add those specific phases back into the quick task workflow.

Does this quick task workflow support plan-checking and post-run validation?

Yes, this quick task workflow supports plan-checking and post-run validation through the --validate flag, which enforces plan verification before execution and runs validation checks after the task completes.

When should I avoid using a lightweight executor for repository changes?

You should avoid using a lightweight executor for repository changes when tasks require extensive research, broad multi-file modifications, or deep discussion, as this workflow is designed for small, well-scoped changes where speed and traceability are prioritized.