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-plan creates the implementation plan for your project. At the project level, it defines all phases. At the phase level, it breaks a single phase into tasks with file targets and acceptance criteria.

​
Invocation

/gg-plan [phase-number]
  • No argument — creates the full project plan, defining all phases and their high-level scope.
  • With a phase number — creates the detailed task breakdown for a single phase, including file targets and acceptance criteria for each task.

​
What It Produces

Project-level plan:
  • plan.md — the master plan with all phases, their descriptions, dependencies, and ordering
  • phases/{N}-{slug}/phase.md — a phase file for each phase with metadata and task stubs
Phase-level plan:
  • Updated phases/{N}-{slug}/phase.md — detailed task breakdown with file targets, check commands, and acceptance criteria for each task

​
Behavior

Workflows uses your input.md, discussion.md, and research.md to produce the plan. The more context these files contain, the more accurate the plan will be.
/gg-plan requires codebase docs to be present. If you haven’t run /gg-codebase yet, Workflows will ask you to run it first.
  • Validation — after planning, Workflows verifies that all expected phase files were created. If any are missing, Workflows offers to retry.
  • Phase dependencies — the plan captures dependencies between phases. A phase that depends on another will not be eligible for execution until its dependency is complete.
  • Checkpoint — after planning completes, Workflows offers to commit the plan files. You can skip this and commit manually later.
You can re-run /gg-plan for a specific phase to regenerate its task breakdown without affecting other phases. This is useful when requirements change after the initial plan.