sg-quick

Orchestrate quick tasks from GSD planning to Superpowers implementation with state tracking.

2|Updated May 15, 2026
One-click install
npx skills add https://github.com/gyuha/super-gsd --skill sg-quick
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sg-quick
Source: https://github.com/gyuha/super-gsd/tree/main/skills/sg-quick
Command: npx skills add https://github.com/gyuha/super-gsd --skill sg-quick

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of fragile, manual handoff between GSD planning and Superpowers implementation when you only need to complete a small ad-hoc task, not a full multi-stage phase workflow.

Core Features & Use Cases

  • One-command quick pipeline: Initializes a quick task with gsd-sdk, generates a focused PLAN.md via gsd-planner, and immediately hands the plan to superpowers:executing-plans for implementation.
  • Flag-driven guidance: Supports lightweight discussion (--discuss), pre-planning research (--research), plan validation (--validate), or all of the above with --full.
  • State tracking for quick tasks: Updates STATE.md with a Quick Tasks Completed entry marked pending so tracking stays consistent across the handoff.

Quick Start

Run /super-gsd:sg-quick "Add a new endpoint to the API and include basic tests" to get a plan and execute it in one loop with atomic commit and STATE.md tracking.

Frequently Asked Questions about sg-quick

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

FAQPage Schema
How do I plan and execute small code changes without a full phase plan?

To handle small ad-hoc coding changes, run a single command that initializes the task, generates a focused PLAN.md, and immediately executes it without requiring a full multi-stage phase workflow.

How does state tracking work for lightweight engineering tasks?

State tracking for lightweight engineering tasks works by updating a STATE.md file with a pending entry, ensuring execution state remains consistent across the planning and implementation handoff.

Can I validate or research a plan before executing a quick task?

Yes, you can validate or research a plan before execution by passing specific flags like --validate or --research, or use --full to enable discussion, research, and validation all at once.

What is the best way to automate ad-hoc documentation updates end-to-end?

The best way to automate ad-hoc documentation updates is using a one-command quick pipeline that parses optional flags, generates a plan, executes it, and commits both the plan and state files atomically.

When should I avoid using a quick task workflow for code changes?

You should avoid using a quick task workflow for code changes when the task requires a full multi-stage phase plan, as this workflow is specifically designed for small ad-hoc updates and lightweight engineering tasks.