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.

On a complex project, /gg-plan may produce several phases that need to execute in sequence. You finished Phase 1 (database schema) and now you want to run execute and verify on Phase 2 (API endpoints) specifically — without touching Phase 3 (frontend) yet. When you need to advance a specific phase rather than running the full workflow end-to-end, you target it by number. This is also useful for resuming after a pause or retrying a failed step.
If your change is small enough that multi-phase planning feels like overkill, consider /gg-task — it runs the full pipeline in one session with a flat task list instead of separate phases.

​
Prerequisites

  • An active Workflows project — run /gg-status to confirm
  • A plan with phases defined — run /gg-plan if no phases exist yet
  • Codebase docs generated — run /gg-codebase if not done already

​
1. Check Phase State

Run /gg-status to see where each phase is in the pipeline: 
/gg-status
This shows every phase, its current step and status, and what command to run next. A phase at plan/done is ready for /gg-execute. A phase at execute/done is ready for /gg-verify. You can also check a phase’s state directly by opening its file and reading the frontmatter: 
.joggr/.gg/projects/{slug}/phases/{N}-{phase-slug}/phase.md
The step and status fields at the top reflect the current state.
Do not edit the step or status fields in the phase frontmatter. Workflows manages these values — editing them directly will put the phase into an inconsistent state.

​
2. Run the Step Command

Pass the phase number to the corresponding command: 
/gg-execute 2
This runs only Phase 2. Workflows resolves the active project automatically and executes the specified phase. The same pattern works for any step:
  • /gg-discuss 3 — discuss Phase 3
  • /gg-research 1 — research Phase 1
  • /gg-plan 4 — plan Phase 4
  • /gg-verify 2 — verify Phase 2

​
Troubleshooting

The phase may be blocked by a dependency on another phase. Run /gg-status to see which phases need to complete first, then advance those before returning to this phase.
This usually happens when a session was interrupted. Re-run the step command — Workflows will detect the stale state and resume. If it remains stuck, see the Troubleshooting guide for how to reset phase state manually.