Gemini CLI uses AfterTool as the post-tool hook event name, not
PostToolUse (which is Claude Code's event name). The installer was
registering the context monitor under PostToolUse for all runtimes,
causing Gemini to print "Invalid hook event name" warnings on every
run and silently disabling the context monitor.
Changes:
- install.js: use runtime-aware event name (AfterTool for Gemini,
PostToolUse for others) when registering context monitor hook
- install.js: uninstall cleans up both PostToolUse and AfterTool
entries for backward compatibility with existing installs
- gsd-context-monitor.js: runtime-aware hookEventName in output
- docs/context-monitor.md: document both event names with Gemini
example
Closes#750
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Adds automated feedback architecture research to gsd-phase-researcher,
enforces it as Dimension 8 in gsd-plan-checker, and introduces
{phase}-VALIDATION.md as the per-phase validation contract.
Ensures every phase plan includes automated verify commands before
execution begins. Opt-out via workflow.nyquist_validation: false.
Closes#122 (partial), related #117
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Create docs/USER-GUIDE.md as a detailed companion to the README, covering:
- Workflow diagrams (project lifecycle, planning coordination, execution waves, brownfield)
- Command reference with "When to Use" guidance for each command
- Full config.json schema including workflow toggles, git branching, and per-agent model profiles
- Practical usage examples for common scenarios
- Troubleshooting section for common issues
- Recovery quick reference table
Add link from README navigation bar and Configuration section to the User Guide.
Closes#457
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Lists all 25 GSD commands with descriptions
- Organized into logical groups (Setup, Planning, Execution, etc.)
- Mobile-friendly responsive design
- Single-file with inline CSS, no dependencies
