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-verify validates that a phase’s acceptance criteria are met after execution. It checks each criterion defined in the phase plan and produces a verification report with pass/fail statuses.

​
Invocation

/gg-verify [phase-number]
  • No argument — Workflows selects the next phase eligible for verification.
  • With a phase number — verifies the specified phase.

​
What It Produces

  • Verification report — a detailed assessment of each acceptance criterion
  • Updated criterion statuses — each criterion is marked as passed or failed
  • Phase status update — the phase is marked as verified (done) or flagged with failures

​
Behavior

Workflows reads the phase plan, inspects the code changes, and evaluates each acceptance criterion against the current state of the codebase. If all criteria pass, the phase is marked as verified and complete. If some criteria fail, Workflows presents the failures and asks how to proceed:
  • Fix and retry — address the failures and re-run /gg-verify
  • Accept as-is — mark the phase as verified despite failures (an admonition is added to the phase file noting the accepted failures)
  • Re-execute — go back to /gg-execute to fix the issues
/gg-verify requires codebase docs to be present. If you haven’t run /gg-codebase yet, Workflows will ask you to run it first.
When all phases in a project reach verified status, Workflows suggests marking the pull request as ready for review.