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-execute implements a phase. It reads the task list, groups tasks into waves based on file conflicts, executes non-conflicting tasks in parallel, and checkpoints after each wave. Phases run one at a time and respect dependency ordering.
Invocation
- No argument — Workflows selects the next eligible phase automatically.
- With a phase number — executes the specified phase.
What It Produces
- Code changes — new files, modified files, and any other artifacts defined by the task plan
- Updated task statuses — each task is marked as done, skipped, or failed
- Checkpoint commits — after each wave, Workflows offers to commit the progress
Behavior
Wave grouping
Workflows analyzes file targets across all tasks and groups them into waves:- Tasks that touch different files run in the same wave (parallel)
- Tasks that touch the same files run in separate waves (sequential)
- Task dependencies from the plan are respected — if task X depends on task Y, X runs in a later wave
Failure handling
If tasks fail during a wave, Workflows asks how to proceed:- Retry failed — re-run only the failed tasks
- Skip failed — mark failed tasks as skipped and continue to the next wave
- Abort phase — stop execution and checkpoint whatever progress was made
If Workflows detects uncommitted changes in the working tree (likely from a previous interrupted
session), it asks whether to checkpoint them, discard them, or abort so you can handle it
manually.