gsd-quick

Automates ad-hoc tasks with atomic commits and STATE.md tracking via spawned planners and executors.

Updated Jan 25, 2026
One-click install
npx skills add https://github.com/MINT-IA/MINT --skill gsd-quick-mint-ia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-quick
Source: https://github.com/MINT-IA/MINT/tree/main/.claude/skills/gsd-quick
Command: npx skills add https://github.com/MINT-IA/MINT --skill gsd-quick-mint-ia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the execution of small, ad-hoc tasks while guaranteeing traceability through atomic commits and state tracking.

Core Features & Use Cases

  • Atomic task commits: guarantees state-consistent updates with each task.
  • Quick planning and execution: separates quick tasks into a dedicated planning workspace (.planning/quick/) to avoid interfering with longer-term plans.
  • State tracking: updates STATE.md with a quick-tasks summary to keep progress visible.

Quick Start

Ask gsd-quick to perform a clearly defined task with atomic commits and state tracking.

Frequently Asked Questions about gsd-quick

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

FAQPage Schema
How do I automate ad-hoc task execution with atomic commits?

Automate ad-hoc task execution by spawning a planner and executors, guaranteeing atomic commits and state tracking for each task. Results are stored under .planning/quick/.

What is the best way to track quick tasks in STATE.md?

Track quick tasks in STATE.md by summarizing completed work in the Quick Tasks Completed table, keeping progress visible and separate from longer-term plans.

How do I run a full quality pipeline for quick planning tasks?

Run a full quality pipeline for quick tasks by using the --full flag, enabling comprehensive processing alongside the standard quick mode planning and execution workflow.

Can I use focused research and discussion flags for quick task automation?

Use --research for focused research and --discuss for discussion control when automating quick tasks, modifying planning and execution behavior to suit specific task requirements.

Does quick task execution interfere with existing long-term planning workspaces?

Quick task execution does not interfere with long-term plans because it separates quick tasks into a dedicated planning workspace at .planning/quick/, isolating ad-hoc work.

How do I verify and validate plan-checking for automated quick tasks?

Verify automated quick tasks by using the --validate flag, triggering plan-checking and verification processes to ensure state-consistent updates with each atomic commit.