From full-orchestration
Run a four-agent review on a technical spec or implementation plan. Use when a spec or plan needs evaluation from maintainability, security, efficiency, and completeness perspectives. Spawns four reviewer agents that write structured comment files, then merges all comments into the document in a single conflict-free pass.
How this skill is triggered — by the user, by Claude, or both
Slash command
/full-orchestration:spec_reviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**State file**: `.claude/swe-state/{ticket-id}.json`
State file: .claude/swe-state/{ticket-id}.json
Four parallel reviewer agents each write a structured comment file. A single merge pass then inserts all comments into the document, avoiding parallel edit conflicts.
/spec_review .claude/specs/PROJ-123.md # Spec review (2C)
/spec_review .claude/specs/PROJ-123-impl.md # Impl plan review (2E)
Detect mode from path: {ticket-id}.md → spec mode, {ticket-id}-impl.md → impl mode. Extract ticket ID from the filename by stripping suffixes in order: -impl.md, -context.md, .md. The first match wins (e.g., PROJ-123-impl.md → strip -impl.md → PROJ-123; PROJ-123.md → strip .md → PROJ-123).
Locate state: .claude/swe-state/{ticket-id}.json. Read state to get: stages.intake.ticket_file and stages.spec.context_file.
Read: document under review (required), ticket.json (if available), context doc (if available).
Delete any existing comment files from prior invocations before starting:
rm -f .claude/swe-state/{ticket-id}/comments-*.json
Spawn FOUR agents in a SINGLE message. Each writes to its own comment file — no direct document edits.
subagent_type: full-orchestration:{ReviewerName}
max_turns: 10
prompt: |
State file: .claude/swe-state/{ticket-id}.json
Review mode: {spec|impl}
Comment file: .claude/swe-state/{ticket-id}/comments-{ReviewerName}.json
Read state to locate the document under review:
- spec mode: stages.spec.spec_file
- impl mode: stages.spec.impl_plan_file
Also read supporting context from state:
- stages.intake.ticket_file
- stages.spec.context_file
The document may contain comments from prior review iterations
(OPEN or RESOLVED). Follow your re-review instructions for those.
Read the document and supporting files, then write your review
comments to the comment file path above.
Agents: MaintainabilityReviewer, SecurityReviewer, EfficiencyReviewer, CompletenessReviewer.
On agent failure: log warning, proceed with remaining agents.
After all agents complete, merge their comment files into the document in a single pass. This avoids parallel edit conflicts.
| Action | Operation |
|---|---|
add | Find the line containing the anchor text. Insert > **[{SEVERITY} | {ReviewerName} | OPEN]** {comment} after the end of that paragraph (next blank line or heading). If anchor not found, append comment at the end of the document with a note. |
reopen | Find the blockquote line matching anchor. Change RESOLVED to OPEN. If comment field is present, replace the comment text. |
remove | Find and delete the blockquote line matching anchor. |
Read the document and count blockquote comments matching:
> **[{SEVERITY} | {Reviewer} | OPEN]**
Report to caller:
npx claudepluginhub shouenlee/ghcp-dev-plugin --plugin full-orchestrationReviews requirements (docs/brainstorms/) or plan (docs/plans/) documents using parallel persona agents to surface role-specific issues, auto-fix quality problems, and present strategic questions. Use with document path or auto-detect.
Reviews technical specifications using expert personas to identify gaps, risks, and missing considerations. Verifies claims against repositories, discusses resolutions, and applies updates.
Dispatches parallel specialist review agents for code diffs, PRDs, or implementation plans. Operates as a pre-PR quality gate or via /review command.