Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.joggr.ai/llms.txt

Use this file to discover all available pages before exploring further.

Overview

/gg-task runs the complete Workflows pipeline — discuss, research, plan, execute, and verify — in one session. Use it for changes small enough to finish without pausing: bug fixes, config tweaks, single-feature additions, small refactors. For larger work that spans multiple sessions or involves coordinating with other people, use /gg-new instead.

Invocation

/gg-task [slug or description]
If you pass a slug matching an existing task, Workflows resumes it. If you pass a description (or a rough phrase), Workflows derives a slug and creates a new task. If you run /gg-task with no arguments, Workflows lets you choose an existing task to resume or create a new one.

Workflow

/gg-task runs six steps in sequence:
  1. New — Resolve or create the task slug and initialize spec.md
  2. Discuss — Clarify scope, constraints, and acceptance criteria with the AI
  3. Research — Analyze the codebase and gather technical context
  4. Plan — Generate a single plan.md with one or more phases (no separate phase directories)
  5. Execute — Group tasks into conflict-free waves and run them in parallel; checkpoint after each wave
  6. Verify — Validate that all acceptance criteria from spec.md are met
Each step persists its output to spec.md so you can resume from where you left off if the session is interrupted.

What It Produces

A task directory at .joggr/.gg/tasks/{slug}/ containing:
  • spec.md — task description, acceptance criteria, and workflow state (step, status in frontmatter)
  • plan.md — one or more phases with task lists (created during the plan step; single file, no phase directories)

Arguments

ArgumentRequiredDescription
[slug or description]NoExisting task slug to resume, or a description to create a new task (e.g., fix-null-check or fix the null check in pagination)

Behavior

Resuming a task

If a task was interrupted mid-step, /gg-task resumes from the last incomplete step. Workflows reads the step and status fields in spec.md frontmatter to determine where to continue. Completed steps are skipped. Steps interrupted mid-run are retried from the beginning, except execution — which resumes from the last incomplete task.

Review gates

After research and again after planning, Workflows checkpoints the work and opens a review UI before continuing. Both gates offer the same three options:
  • Approve and continue — proceeds to the next step
  • Save and stop — checkpoints and exits; resume later with /gg-task your-task-slug
  • Skip review — proceeds without opening the UI

Archiving

After verification, /gg-task offers to archive the task. Archiving zips the task directory to .joggr/.gg/.archive/, deletes the source directory, and removes the task from /gg-status.
Quick Mode skips phase files entirely. There is no phases/ directory, no phase state, and no /gg-plan or /gg-execute phase commands. The entire workflow lives in spec.md and plan.md.

For a conceptual overview and worked examples, see Tasks.