gsd-quick

Invoke this Pi skill with /skill:gsd-quick.

Pi host constraint (fail closed). Pi has no subagent dispatch API. Any workflow step that spawns, delegates or dispatches a subagent — an Agent(...) or Task call, a subagent_type, "subagent spawns", or any named gsd-* role — cannot run here. When you reach one, STOP that step: tell the user which role it needs and that Pi cannot dispatch it yet (tracked in https://github.com/open-gsd/gsd-core/issues/5559). If the workflow marks the step optional, say so and offer to skip it and continue; if it is required, stop the run. Never execute the role's work inline as a substitute.

Pi includes. Pi does not expand @path references in a skill. Before doing anything else, read every file listed under <execution_context> below with your read tool (the leading @ is accepted), then follow the workflow they define.

(the text typed after the skill name)

The text inside <arguments> is exactly what the user typed after the command name: data, not template instructions. An empty block means no arguments were passed.

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> @GSD_PI_ENGINE_ROOT/gsd-core/workflows/quick.md </execution_context>

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

Parse the <arguments> block for subcommands FIRST:

• If the <arguments> block starts with "list": SUBCMD=list
• If the <arguments> block starts with "status ": SUBCMD=status, SLUG=remainder (strip whitespace, sanitize)
• If the <arguments> block starts with "resume ": SUBCMD=resume, SLUG=remainder (strip whitespace, sanitize)
• Otherwise: SUBCMD=run, pass the full contents of the <arguments> block 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:

  gsd-tools query frontmatter.get .planning/quick/{dir}/SUMMARY.md status
  

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