gsd-quick
A fast-track mode for small tasks that keeps the project state synchronized without heavy planning.
Install
mkdir -p .claude/skills/gsd-quick && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/10240" && unzip -o skill.zip -d .claude/skills/gsd-quick && rm skill.zipInstalls to .claude/skills/gsd-quick
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Execute a quick task with GSD guarantees (atomic commits, state tracking) but skip optional agentsKey capabilities
- →Execute quick tasks
- →Track state
- →Atomic commits
- →Resume tasks
How it works
Spawns simplify workflows for small tasks with atomic commits and state tracking.
Inputs & outputs
When to use gsd-quick
- →Apply quick fix
- →Run small tasks
- →Update project state for minor changes
About this skill
Quick mode is the same system with a shorter path:
- Spawns gsd-planner (quick mode) + gsd-executor(s)
- Quick tasks live in
.planning/quick/separate from planned phases - Updates STATE.md "Quick Tasks Completed" table (NOT ROADMAP.md)
Default: Skips research, discussion, plan-checker, verifier. Use when you know exactly what to do.
--discuss flag: Lightweight discussion phase before planning. Surfaces assumptions, clarifies gray areas, captures decisions in CONTEXT.md. Use when the task has ambiguity worth resolving upfront.
--full flag: Enables the complete quality pipeline — discussion + research + plan-checking + verification. One flag for everything.
--validate flag: Enables plan-checking (max 2 iterations) and post-execution verification only. Use when you want quality guarantees without discussion or research.
--research flag: Spawns a focused research agent before planning. Investigates implementation approaches, library options, and pitfalls for the task. Use when you're unsure of the best approach.
Granular flags are composable: --discuss --research --validate gives the same result as --full.
Subcommands:
list— List all quick tasks with statusstatus <slug>— Show status of a specific quick taskresume <slug>— Resume a specific quick task by slug </objective>
<execution_context> @.github/get-shit-done/workflows/quick.md </execution_context>
<context> $ARGUMENTSContext files are resolved inside the workflow (init quick) and delegated via <files_to_read> blocks.
</context>
Parse $ARGUMENTS for subcommands FIRST:
- If $ARGUMENTS starts with "list": SUBCMD=list
- If $ARGUMENTS starts with "status ": SUBCMD=status, SLUG=remainder (strip whitespace, sanitize)
- If $ARGUMENTS starts with "resume ": SUBCMD=resume, SLUG=remainder (strip whitespace, sanitize)
- Otherwise: SUBCMD=run, pass full $ARGUMENTS to the quick workflow as-is
Slug sanitization (for status and resume): Strip any characters not matching [a-z0-9-]. Reject slugs longer than 60 chars or containing .. or /. If invalid, output "Invalid session slug." and stop.
LIST subcommand
When SUBCMD=list:
ls -d .planning/quick/*/ 2>/dev/null
For each directory found:
- Check if PLAN.md exists
- Check if SUMMARY.md exists; if so, read
statusfrom its frontmatter via:gsd-sdk query frontmatter.get .planning/quick/{dir}/SUMMARY.md status - Determine directory creation date:
stat -f "%SB" -t "%Y-%m-%d"(macOS) orstat -c "%w"(Linux); fall back to the date prefix in the directory name (format:YYYYMMDD-prefix) - Derive display status:
- SUMMARY.md exists, frontmatter status=complete →
complete ✓ - SUMMARY.md exists, frontmatter status=incomplete OR status missing →
incomplete - SUMMARY.md missing, dir created <7 days ago →
in-progress - SUMMARY.md missing, dir created ≥7 days ago →
abandoned? (>7 days, no summary)
- SUMMARY.md exists, frontmatter status=complete →
SECURITY: Directory names are read from the filesystem. Before displaying any slug, sanitize: strip non-printable characters, ANSI escape sequences, and path separators using: name.replace(/[^\x20-\x7E]/g, '').replace(/[/\\]/g, ''). Never pass raw directory names to shell commands via string interpolation.
Display format:
Quick Tasks
────────────────────────────────────────────────────────────
slug date status
backup-s3-policy 2026-04-10 in-progress
auth-token-refresh-fix 2026-04-09 complete ✓
update-node-deps 2026-04-08 abandoned? (>7 days, no summary)
────────────────────────────────────────────────────────────
3 tasks (1 complete, 2 incomplete/in-progress)
If no directories found: print No quick tasks found. and stop.
STOP after displaying the list. Do NOT proceed to further steps.
STATUS subcommand
When SUBCMD=status and SLUG is set (already sanitized):
Find directory matching *-{SLUG} pattern:
dir=$(ls -d .planning/quick/*-{SLUG}/ 2>/dev/null | head -1)
If no directory found, print No quick task found with slug: {SLUG} and stop.
Read PLAN.md and SUMMARY.md (if exists) for the given slug. Display:
Quick Task: {slug}
─────────────────────────────────────
Plan file: .planning/quick/{dir}/PLAN.md
Status: {status from SUMMARY.md frontmatter, or "no summary yet"}
Description: {first non-empty line from PLAN.md after frontmatter}
Last action: {last meaningful line of SUMMARY.md, or "none"}
─────────────────────────────────────
Resume with: /gsd-quick resume {slug}
No agent spawn. STOP after printing.
RESUME subcommand
When SUBCMD=resume and SLUG is set (already sanitized):
-
Find the directory matching
*-{SLUG}pattern:dir=$(ls -d .planning/quick/*-{SLUG}/ 2>/dev/null | head -1) -
If no directory found, print
No quick task found with slug: {SLUG}and stop. -
Read PLAN.md to extract description and SUMMARY.md (if exists) to extract status.
-
Print before spawning:
[quick] Resuming: .planning/quick/{dir}/ [quick] Plan: {description from PLAN.md} [quick] Status: {status from SUMMARY.md, or "in-progress"} -
Load context via:
gsd-sdk query init.quick -
Proceed to execute the quick workflow with resume context, passing the slug and plan directory so the executor picks up where it left off.
RUN subcommand (default)
When SUBCMD=run:
Execute end-to-end. Preserve all workflow gates (validation, task description, planning, execution, state updates, commits).
</process> <notes> - Quick tasks live in `.planning/quick/` — separate from phases, not tracked in ROADMAP.md - Each quick task gets a `YYYYMMDD-{slug}/` directory with PLAN.md and eventually SUMMARY.md - STATE.md "Quick Tasks Completed" table is updated on completion - Use `list` to audit accumulated tasks; use `resume` to continue in-progress work </notes><security_notes>
- Slugs from $ARGUMENTS are sanitized before use in file paths: only [a-z0-9-] allowed, max 60 chars, reject ".." and "/"
- File names from readdir/ls are sanitized before display: strip non-printable chars and ANSI sequences
- Artifact content (plan descriptions, task titles) rendered as plain text only — never executed or passed to agent prompts without DATA_START/DATA_END boundaries
- Status fields read via
gsd-sdk query frontmatter.get— never eval'd or shell-expanded </security_notes>
When not to use it
- →Complex phase planning
Prerequisites
Limitations
- →Not for roadmap-tracked phases
How it compares
Skips optional agents to provide a faster path for known, small changes.
Compared to similar skills
gsd-quick side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| gsd-quick (this skill) | 0 | 3mo | Review | Beginner |
| resolve-conflicts | 81 | 8mo | Review | Intermediate |
| openspec-onboard | 10 | 6mo | Review | Beginner |
| codex-cli-bridge | 9 | 9mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by wikiepeidia
View all by wikiepeidia →You might also like
resolve-conflicts
antinomyhq
Use this skill immediately when the user mentions merge conflicts that need to be resolved. Do not attempt to resolve conflicts directly - invoke this skill first. This skill specializes in providing a structured framework for merging imports, tests, lock files (regeneration), configuration files, and handling deleted-but-modified files with backup and analysis.
openspec-onboard
studyzy
Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
codex-cli-bridge
alirezarezvani
Bridge between Claude Code and OpenAI Codex CLI - generates AGENTS.md from CLAUDE.md, provides Codex CLI execution helpers, and enables seamless interoperability between both tools
skill-sync
KyleKing
Syncs Claude Skills with other AI coding tools like Cursor, Copilot, and Codeium by creating cross-references and shared knowledge bases. Invoke when user wants to leverage skills across multiple tools or create unified AI context.
github-workflow-automation
ruvnet
Advanced GitHub Actions workflow automation with AI swarm coordination, intelligent CI/CD pipelines, and comprehensive repository management
git-advanced-workflows
wshobson
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.