gsd-quick

Execute small ad-hoc tasks with GSD guarantees and atomic commits.

4|1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/lgwanai/openforce --skill gsd-quick-lgwanai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-quick
Source: https://github.com/lgwanai/openforce/tree/main/skills/gsd-quick
Command: npx skills add https://github.com/lgwanai/openforce --skill gsd-quick-lgwanai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you execute small, ad-hoc work items with GSD guarantees like atomic commits and state tracking, while skipping heavy phases when you already know what to do.

Core Features & Use Cases

  • Quick-mode execution: Runs the GSD pipeline in quick mode by invoking gsd-planner (quick mode) and one or more gsd-executor agents, storing quick artifacts under .planning/quick/ instead of planned phases.
  • State tracking for auditing: Updates STATE.md with a “Quick Tasks Completed” table and uses per-task directories (YYYYMMDD-{slug}/) with PLAN.md and eventually SUMMARY.md.
  • Quality controls via flags: Defaults to skipping research, discussion, plan-checker, and verifier; you can selectively add --discuss, --research, and --validate, or enable everything with --full.
  • Operational subcommands: Supports list, status <slug>, and resume <slug> for managing in-flight quick tasks without rerunning everything.

Quick Start

Run the quick workflow for your task by typing: openforce /gsd-quick "fix the authentication token refresh for API clients".

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 and state tracking?

To automate ad-hoc task execution with atomic commits and state tracking, run a quick planning and execution pipeline that stores artifacts under .planning/quick and updates STATE.md automatically.

What is the best way to skip heavy planning phases for small workflow automation tasks?

Skipping heavy planning phases for workflow automation is achieved by using a quick mode that defaults to omitting research, discussion, and validation, allowing direct execution of small tasks.

Can I selectively enable plan validation and research when running quick tasks?

You can selectively enable plan validation and research by applying specific flags like --validate, --research, --discuss, or use --full to activate all optional quality controls during execution.

How do I resume an interrupted workflow automation task by its slug?

Resuming an interrupted workflow automation task by its slug uses the resume subcommand, which restores in-flight quick tasks without rerunning the entire pipeline from the beginning.

How does state tracking work for small ad-hoc tasks?

State tracking for small ad-hoc tasks works by appending entries to a Quick Tasks Completed table in STATE.md and generating per-task directories containing PLAN.md and SUMMARY.md files.

Does this quick task execution approach require external dependencies?

This quick task execution approach requires no external dependencies, relying solely on internal planner and executor agents to manage state tracking and atomic commit behavior.