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-discuss runs a structured interview to gather context, requirements, and preferences before you plan or execute. It systematically covers goals, constraints, preferences, edge cases, and acceptance criteria across multiple rounds of questions.

​
Invocation

/gg-discuss [phase-number]
  • No argument — runs at the project level, covering the entire project scope. This is the typical usage before your first /gg-plan.
  • With a phase number — runs at the phase level, focusing the discussion on a specific phase’s requirements.

​
What It Produces

Timestamped entries appended to discussion.md in your project directory. Each round of questions and your responses is recorded with an ISO 8601 timestamp, preserving a complete audit trail of decisions. 
### 2026-04-03T14:30:00Z

**Question:** What are the primary goals for this feature?

> Support paginated listing of user profiles with cursor-based pagination

​
Behavior

Workflows asks 2—4 questions per round, grouped by topic area. After each round, Workflows shows which areas have been covered and which remain. The five probe areas are:
  1. Goals — primary objectives, success metrics, desired outcomes
  2. Constraints — backward compatibility, performance, resource limits
  3. Preferences — preferred libraries, code patterns, architecture
  4. Edge cases — failure scenarios, error conditions, security concerns
  5. Acceptance criteria — definition of done, testing requirements, deployment considerations
You can exit the discussion at any time. Workflows detects phrases like “enough”, “move on”, or “done” and offers to wrap up. Uncovered areas default to the context already captured in input.md.
Running /gg-discuss multiple times appends new entries — it never overwrites previous responses. This means you can revisit the discussion as your understanding evolves.