For simple tasks, agents work fine on their own. For complex features (multi-file refactors, new systems, cross-cutting changes) they lose track, make contradictory decisions, and produce work that needs heavy rework. And without structure, you’re merging 800-line PRs you skimmed for 2 minutes. Workflows gives agents structure and gives you reviewable checkpoints.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.
What are Workflows
Workflows is Joggr’s Guided Generative Workflow engine (GG) — a structured pipeline that moves work through discuss, research, plan, execute, and verify. Instead of throwing an agent at a vague prompt and hoping for the best, you get clear deliverables and human review gates at every stage. Workflows operates in two modes depending on the size and complexity of the work:Quick Mode
For small, well-scoped changes. Run
/gg-task and complete the entire pipeline in a single
session — no project scaffolding, no separate phase files. Two artifacts (spec.md and
plan.md) in the tasks/ directory.Standard Mode
For complex, multi-phase features. Run
/gg-new to scaffold a full project with separate
discuss, research, plan, execute, and verify stages. Each phase has its own review gate and
produces durable artifacts in the projects/ directory.Why Workflows
Agents are great at executing well-defined tasks. They’re terrible at managing ambiguity over long-running work. Without structure, they accumulate errors, lose context, and produce code that technically works but doesn’t fit your architecture. You become the project manager: breaking work into phases, feeding context between steps, and stitching results into reviewable PRs. Workflows solves three problems:- Decomposition — work gets broken into concrete tasks with acceptance criteria. In Standard Mode, tasks are grouped into phases. In Quick Mode, they’re a flat list.
- Review gates — you see the plan before code gets written. You review changes before they ship. No surprises at the end.
- Continuity — every stage builds on the last. Requirements inform the plan, the plan drives execution, execution is verified against what was planned. No context loss, no contradictory decisions.
Standard Mode — Multi-Phase Projects
Standard Mode is the full pipeline for complex work. You invoke each stage separately and review between stages.
Discuss & Research
Tell Workflows what you want to build. It runs a structured interview to capture your goals,
constraints, preferences, edge cases, and acceptance criteria — then analyzes your codebase to
find relevant patterns, dependencies, and conventions.
Review the plan
Workflows breaks the work into phases and tasks with file targets, check commands, and
acceptance criteria. You review and approve the plan before a single line of code is written.
Use
/gg-review to open the plan in a local review UI where
you can leave inline annotations, or review it directly in the terminal.Execute
Workflows groups tasks into waves — non-conflicting tasks run in parallel, conflicting ones in
sequence. Runs validation (typecheck, lint, tests) after each task and commits progress
automatically. If the process crashes, Workflows detects the stale state on next run and resumes
cleanly.
/gg-new. See Projects for details on project structure and lifecycle.
Quick Mode — Single-Session Tasks
Quick Mode runs the entire pipeline in one invocation of/gg-task. No project scaffolding, no separate phase directories — just a spec and a plan in the tasks/ directory.
Research
Codebase analysis. The researcher agent identifies relevant files and surfaces implementation
approaches. Review gate opens before planning.
Plan
Task list generation. The planner produces
plan.md with one or more phases. Review gate opens
before execution.Execute
Tasks grouped into conflict-free waves and run in parallel. Checkpoint and confirm after each
wave.
/gg-task followed by a description or slug. See Tasks for the full guide.
Choosing a Mode
| Factor | Quick Mode (/gg-task) | Standard Mode (/gg-new) |
|---|---|---|
| Scope | Single concern — a bug fix, a rename, a small feature | Multi-file features, cross-cutting refactors |
| Invocation | One command runs the full pipeline | Separate command per stage |
| Artifacts | spec.md + plan.md in tasks/ | Full project directory with phase files in projects/ |
| Planning depth | Flat task list | Multi-phase plan with dependencies between phases |
| Review gates | Inline during the session | Explicit gates between discuss, plan, execute, and verify |