gsd-quick

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

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/WeWake1/BSOMS --skill gsd-quick-wewake1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-quick
Source: https://github.com/WeWake1/BSOMS/tree/main/.agent/skills/gsd-quick
Command: npx skills add https://github.com/WeWake1/BSOMS --skill gsd-quick-wewake1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Small, ad-hoc development tasks often fall outside structured milestone planning, leaving them untracked, uncommitted atomically, and disconnected from project state. This Skill runs quick tasks through a lightweight GSD workflow that preserves atomic commits and state tracking without the overhead of full planning ceremonies. ## Core Features & Use Cases - Quick Task Execution: Spawns a gsd-planner in quick mode plus gsd-executor agents, storing tasks in .planning/quick/ separate from planned phases. - State Tracking: Updates the STATE.md "Quick Tasks Completed" table instead of ROADMAP.md, keeping quick work visible in project history. - Composable Flags: Supports --discuss (lightweight discussion captured in CONTEXT.md), --research (focused research agent before planning), and --full (plan-checking plus post-execution verification), which can be combined. - Use Case: A developer needs to fix a small bug or add a minor config change. Instead of creating a full milestone plan, they run the quick workflow so the change is planned, executed, committed atomically, and recorded in STATE.md. ## Quick Start Ask the agent to run a quick task describing what you want done, optionally adding flags like --discuss or --full for extra rigor.

Frequently Asked Questions about gsd-quick

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

FAQPage Schema
How do I run a quick task with the GSD workflow?

Invoke the gsd-quick skill with a description of the task. It spawns a gsd-planner in quick mode and gsd-executor agents, then runs the quick workflow end-to-end including validation, planning, execution, state updates, and atomic commits.

What is the difference between quick mode and full GSD planning?

Quick mode skips research, discussion, plan-checker, and verifier agents by default, and stores tasks in .planning/quick/ instead of planned phases. It updates the STATE.md Quick Tasks Completed table rather than ROADMAP.md.

Can I combine the --discuss, --research, and --full flags?

Yes, the flags are composable. For example, --discuss --research --full gives you a discussion phase, a focused research agent, plan-checking with up to two iterations, and post-execution verification in a single quick run.

When should I use the --full flag on a quick task?

Use --full when you want quality guarantees without full milestone ceremony. It enables plan-checking with a maximum of two iterations and post-execution verification, which suits tasks where correctness matters but scope is still small.

Where are quick tasks stored and tracked?

Quick tasks live in the .planning/quick/ directory, separate from planned phases. Completion is recorded in the STATE.md Quick Tasks Completed table, not in ROADMAP.md.