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.

A project is the container for a single piece of work moving through the Guided Generative Workflow (GG) pipeline — from /gg-new through discuss, research, plan, execute, and verify. Every artifact Workflows produces lives inside it: discussion notes, research findings, the plan, and phase files.

​
Projects and Phases

The Guided Generative Workflow pipeline operates at two levels:
  • Project — the planning container. /gg-discuss, /gg-research, and /gg-plan run once at the project level and produce the plan.
  • Phase — the execution unit. /gg-plan breaks the work into one or more phases. Each phase is then executed and verified independently with /gg-execute and /gg-verify.
A simple project typically has a single phase — the full workflow feels linear end-to-end. A complex project might have several phases that execute in sequence, each building on the last. You create a project with /gg-new, which scaffolds the directory and sets the project as active.

​
Directory Structure

Each project lives at .joggr/.gg/projects/{slug}/ in your repository. The slug is a lowercase, hyphen-separated identifier you choose when creating the project (for example, auth-refactor or webhook-endpoint).
FileProduced ByPurpose
input.md/gg-newRaw requirements, goals, constraints, and links you provided when creating the project. This is the seed for all downstream stages.
discussion.md/gg-discussTimestamped Q&A rounds organized by probe area (goals, constraints, preferences, edge cases, acceptance criteria). Appended to across multiple sessions.
research.md/gg-researchTechnical findings: architecture patterns, dependencies, existing code conventions, external documentation references, and risk assessment.
overview.md/gg-newProject summary, goals, scope, and acceptance criteria. Populated by /gg-plan once planning is complete.
plan.md/gg-planThe implementation plan: phase breakdown, task lists, file targets, check commands, and acceptance criteria.
phases/{N}-{slug}/phase.md/gg-planPer-phase task file with detailed task descriptions, file targets, and acceptance criteria. Used by /gg-execute to run tasks.
These files are committed to your repository. They serve as both working state for Workflows and a permanent record of the decisions and context behind each project.

​
Tasks Directory

Not every change needs a full project. For small, well-scoped work — a bug fix, a rename, a config tweak — use /gg-task instead of /gg-new. Tasks live in a separate directory:
Tasks produce two artifacts instead of a full project directory — no phase subdirectories, no separate discussion or research files. The tasks/ and projects/ directories are independent; one does not affect the other. See Tasks for the full guide. Workflows’ repo-level settings (checkpoint behavior, execution modes) live separately in .joggr/.gg/settings.json. See Configuration for details.

​
Working with Multiple Projects

Workflows resolves the active project automatically — you don’t need to manage this manually. When you run a command, it uses the following priority:
1

Last set project

If a project was set as active (by /gg-new or a previous session), Workflows uses it.
2

Single project fallback

If no active project is set but only one project exists, Workflows uses it automatically.
3

Ambiguous prompt

If multiple projects exist and none is set as active, Workflows presents a list and asks you to choose.
Your projects are visible directly in .joggr/.gg/projects/ — each subdirectory is a project. If you need to manually switch the active project, run /gg-new and choose “Resume” on an existing project, or run /gg-status to see which project is currently active.