Files
msd-core/commands/gsd/quick.md
Tom Boucher 7b07dde150 feat: add list/status/resume/close subcommands to /gsd-quick and /gsd-thread (#2159)
* feat(2155): add list/status/resume subcommands and security hardening to /gsd-quick

- Add SUBCMD routing (list/status/resume/run) before quick workflow delegation
- LIST subcommand scans .planning/quick/ dirs, reads SUMMARY.md frontmatter status
- STATUS subcommand shows plan description and current status for a slug
- RESUME subcommand finds task by slug, prints context, then resumes quick workflow
- Slug sanitization: only [a-z0-9-], max 60 chars, reject ".." and "/"
- Directory name sanitization for display (strip non-printable + ANSI sequences)
- Add security_notes section documenting all input handling guarantees

* feat(2156): formalize thread status frontmatter, add list/close/status subcommands, remove heredoc injection risk

- Replace heredoc (cat << 'EOF') with Write tool instruction — eliminates shell injection risk
- Thread template now uses YAML frontmatter (slug, title, status, created, updated fields)
- Add subcommand routing: list / list --open / list --resolved / close <slug> / status <slug>
- LIST mode reads status from frontmatter, falls back to ## Status heading
- CLOSE mode updates frontmatter status to resolved via frontmatter set, then commits
- STATUS mode displays thread summary (title, status, goal, next steps) without spawning
- RESUME mode updates status from open → in_progress via frontmatter set
- Slug sanitization for close/status: only [a-z0-9-], max 60 chars, reject ".." and "/"
- Add security_notes section documenting all input handling guarantees

* test(2155,2156): add quick and thread session management tests

- quick-session-management.test.cjs: verifies list/status/resume routing,
  slug sanitization, directory sanitization, frontmatter get usage, security_notes
- thread-session-management.test.cjs: verifies list filters (--open/--resolved),
  close/status subcommands, no heredoc, frontmatter fields, Write tool usage,
  slug sanitization, security_notes
2026-04-12 10:05:17 -04:00

7.3 KiB

name, description, argument-hint, allowed-tools
name description argument-hint allowed-tools
gsd:quick Execute a quick task with GSD guarantees (atomic commits, state tracking) but skip optional agents [list | status <slug> | resume <slug> | --full] [--validate] [--discuss] [--research] [task description]
Read
Write
Edit
Glob
Grep
Bash
Task
AskUserQuestion
Execute small, ad-hoc tasks with GSD guarantees (atomic commits, STATE.md tracking).

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 status
  • status <slug> — Show status of a specific quick task
  • resume <slug> — Resume a specific quick task by slug

<execution_context> @~/.claude/get-shit-done/workflows/quick.md </execution_context>

$ARGUMENTS

Context files are resolved inside the workflow (init quick) and delegated via <files_to_read> blocks.

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 status from its frontmatter via:
    node "$HOME/.claude/get-shit-done/bin/gsd-tools.cjs" frontmatter get .planning/quick/{dir}/SUMMARY.md --field status 2>/dev/null
    
  • Determine directory creation date: stat -f "%SB" -t "%Y-%m-%d" (macOS) or stat -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)

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):

  1. Find the directory matching *-{SLUG} pattern:

    dir=$(ls -d .planning/quick/*-{SLUG}/ 2>/dev/null | head -1)
    
  2. If no directory found, print No quick task found with slug: {SLUG} and stop.

  3. Read PLAN.md to extract description and SUMMARY.md (if exists) to extract status.

  4. Print before spawning:

    [quick] Resuming: .planning/quick/{dir}/
    [quick] Plan: {description from PLAN.md}
    [quick] Status: {status from SUMMARY.md, or "in-progress"}
    
  5. Load context via:

    node "$HOME/.claude/get-shit-done/bin/gsd-tools.cjs" init quick
    
  6. 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 the quick workflow from @~/.claude/get-shit-done/workflows/quick.md end-to-end. Preserve all workflow gates (validation, task description, planning, execution, state updates, commits).

- 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

<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-tools.cjs frontmatter get — never eval'd or shell-expanded </security_notes>