skills.rest
coco-research
coco-researchCOMMUNITY
Explore all skills by this author →
GitHub

gsd-quick

Execute small GSD tasks with atomic commits and STATE.md updates.

264|11|Updated Apr 25, 2026
Search Tags:#workflow#planning#validation#task execution#atomic commits#state tracking#gsd
One-click install
npx skills add https://github.com/coco-research/coco --skill gsd-quick-coco-research
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-quick
Source: https://github.com/coco-research/coco/tree/main/systems/gsd/skills/gsd-quick
Command: npx skills add https://github.com/coco-research/coco --skill gsd-quick-coco-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you complete small, ad-hoc development tasks with GSD guarantees, including atomic commits and state tracking, without the overhead of the full multi-agent workflow.

Core Features & Use Cases

  • Quick execution path: Uses a shorter workflow that goes from task intake to execution faster than the full GSD process.
  • Optional quality gates: Supports discussion, research, validation, and full pipeline modes when a task needs more certainty.
  • Persistent task bookkeeping: Tracks quick tasks in STATE.md and keeps them separate from planned phases in .planning/quick/.
  • Use case: Ideal for a clearly scoped bug fix, refactor, or small feature change where you already know the desired outcome.

Quick Start

Ask the assistant to run the gsd-quick workflow for your task and include any optional flags such as --validate, --discuss, --research, or --full if you want extra checks.

Frequently Asked Questions about gsd-quick

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

FAQPage Schema
How do I execute small bug fixes or refactors with atomic commits and state tracking?▼

To execute small development tasks with atomic commits and state tracking, run a quick workflow that applies changes, updates STATE.md, and commits the results without invoking a full multi-agent process.

What is the best way to handle ad-hoc development tasks separately from planned phases?▼

Handling ad-hoc development tasks separately from planned phases requires persistent task bookkeeping, which tracks quick tasks in a dedicated directory and records their state independently in STATE.md.

Can I add validation gates and research steps to a quick task execution path?▼

Yes, you can add validation gates and research steps to a quick task execution path by passing optional flags like --validate, --discuss, or --research when you start the workflow.

Does a shortened planning path workflow still support optional discussion and full pipeline modes?▼

A shortened planning path workflow supports optional discussion, research, validation, and full pipeline modes to provide extra certainty when a clearly scoped task requires deeper analysis.

When should I avoid using a quick workflow for task execution?▼

You should avoid using a quick workflow for task execution when your development work lacks a clearly scoped desired outcome or requires the comprehensive overhead of a full multi-agent planning and execution process.

Related Skills

Explore More Software Engineering Skills→
BellaBeBellaBe
37

planning-action

Translate goals into phased plans with milestones and dependencies.

Community
Advanced
whoabuddywhoabuddy
2

quest-exec

Orchestrate planned phase execution across tasks with isolated subagents and atomic commits.

Community
Advanced
aslaiiaslaii

gsd-quick

Execute ad-hoc tasks with atomic commits and STATE.md tracking via quick workflow.

Community
Intermediate
nnexainnexai
1

gsd-ns-workflow

Coordinates multi-step AI workflows through planning, execution, and verification phases.

Community
Advanced