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.

Guided Generative Workflows is AI-powered. It can be wrong. That is expected behavior, not a bug — and every part of the workflow is designed to be recoverable.

​
Review Before Proceeding

The single most important habit: read what Workflows produced at each step before moving to the next.
  • After /gg-discuss — read discussion.md. Did it capture your intent accurately?
  • After /gg-research — read research.md. Did it find the right files and patterns?
  • After /gg-plan — read plan.md. Are the tasks scoped correctly? Are the file targets right?
  • After /gg-execute — review the code changes. Do they match the plan?
  • After /gg-verify — check the pass/fail report. Do the results make sense?
Each step builds on the previous one. A misunderstanding in the discuss phase compounds through research, planning, and execution. Catching it early saves time.

​
Troubleshooting

This can happen if discussion.md was not saved properly. Check that the file exists and contains your previous responses:
cat .joggr/.gg/projects/my-project/discussion.md
If it is empty or missing, the discussion was not checkpointed. Re-run /gg-discuss to start fresh.
The research phase relies on codebase docs generated by /gg-codebase. If your codebase has changed significantly since the last scan, re-run /gg-codebase to refresh the docs, then re-run /gg-research.
Workflows does not always catch compilation errors during execution. After /gg-execute, run your project’s build and test commands manually. If there are issues, fix them yourself or re-run /gg-execute with more context added to the plan.