with one click
gsd-review
Request cross-AI peer review of phase plans from external AI CLIs
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
Request cross-AI peer review of phase plans from external AI CLIs
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Create detailed phase plan (PLAN.md) with verification loop
File a phase artifact into MemPalace; mirror decision facts into its temporal KG
Cross-AI plan convergence - replan until review concerns are resolved.
Generate an AI-SPEC.md design contract for phases that involve building AI systems.
Start a new milestone cycle — update PROJECT.md and route to requirements
Toggle which skills are surfaced — apply a profile, list, or disable a cluster without reinstall
| name | gsd-review |
| description | Request cross-AI peer review of phase plans from external AI CLIs |
| argument-hint | --phase N [--gemini] [--claude] [--codex] [--opencode] [--qwen] [--cursor] [--agy] [--all] |
| allowed-tools | ["Read","Write","Bash","Glob","Grep"] |
Flow: Detect CLIs → Build review prompt → Invoke each CLI → Collect responses → Write REVIEWS.md
<execution_context> @~/.claude/gsd-core/workflows/review.md </execution_context>
Phase number: extracted from $ARGUMENTS (required)Flags:
--gemini — Include Gemini CLI review--claude — Include Claude CLI review (uses separate session)--codex — Include Codex CLI review--opencode — Include OpenCode review (uses model from user's OpenCode config)--qwen — Include Qwen Code review (Alibaba Qwen models)--cursor — Include Cursor agent review--agy / --antigravity — Include Antigravity CLI review--all — Include all available CLIsNo flags — if review.default_reviewers is set, review with only those configured
reviewers that are detected; otherwise review with all available CLIs. Configured
review.reviewer_instances names may appear in review.default_reviewers; each runs as an
independent reviewer identity backed by its configured adapter+model (see
docs/CONFIGURATION.md). Instance names are not valid as flags.