feat(readiness): add /production-readiness-review parallel multi-agent review command#247
Conversation
…t review command Fans blind reviewers across performance, security, UI/UX, and test coverage, each grounding findings in real state, then reconciles into one deduplicated severity-ranked punch-list. Report-only: never fixes, merges, or deploys. Command-only, distributed via the plugin bundle. Closes R13 from the 2026-06-17 report-coverage map. Plan: docs/plans/2026-06-17-production-readiness-review-command.md
There was a problem hiding this comment.
Code Review
This pull request introduces the /production-readiness-review command, which orchestrates a parallel multi-agent readiness gate fanning across performance, security, UI/UX, and test coverage, and then reconciles findings into a prioritized punch-list. The changes include the command specification, its design plan, and the generated plugin mirror. Feedback on the design plan suggests removing code-reviewer from the list of cited agents to accurately reflect the actual implementation, which only routes through security-auditor and test-engineer.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
| ## Risks | ||
|
|
||
| - `doc-runtime-claims` false-trip if the prose claims a runtime gate — keep it framed as orchestration/advice. | ||
| - Cited agents (`code-reviewer`, `security-auditor`, `test-engineer`) and `superpowers:dispatching-parallel-agents` must exist — all confirmed present. |
There was a problem hiding this comment.
The plan lists code-reviewer under the "Cited agents" risk check, but the /production-readiness-review command itself does not cite or route through the code-reviewer agent (it only routes through security-auditor and test-engineer). To keep the plan accurate and aligned with the actual implementation, we should remove code-reviewer from this list.
| - Cited agents (`code-reviewer`, `security-auditor`, `test-engineer`) and `superpowers:dispatching-parallel-agents` must exist — all confirmed present. | |
| - Cited agents (security-auditor, test-engineer) and superpowers:dispatching-parallel-agents must exist — all confirmed present. |
Summary
Adds
/production-readiness-review, the review-side sibling of/ship: it fans blind specialized reviewers across performance, security, UI/UX, and test coverage — each grounding findings in real code, logs, or live data — then reconciles them into one deduplicated, severity-ranked punch-list. Report-only; it never fixes, merges, or deploys.Closes R13 from the 2026-06-17 report-coverage map: the parallel-review pieces already existed (
superpowers:dispatching-parallel-agents+ the severity-ratingsecurity-auditor/test-engineeragents) but nothing bound them into a named readiness gate.What it does
dispatching-parallel-agentslaunches four blind reviewers (perf/bundle; security/data-access viasecurity-auditor; UI/UX via Playwright when available, else static; test coverage/flaky-mocks viatest-engineer), each forbidden from assuming or fabricating state./shiprun.Scope
commands/production-readiness-review.md(command-only) + generated mirror + plan doc..mtscode; no auto-fix (report-only); no merge/deploy; not added to theproceed-with-the-recommendationrouting table (sorouting-targetsis untouched).Files
commands/production-readiness-review.md— hand-authored sourceplugins/continuous-improvement/commands/production-readiness-review.md— generated mirror (npm run build)docs/plans/2026-06-17-production-readiness-review-command.md— planVerification
npm run verify:all— green (12/12 invariants + typecheck: everything-mirror 59/59, routing-targets 37/37, tool-count expert=19 / beginner=4, doc-runtime-claims clean — the command avoids runtime-gate phrasing).install.test— 29/29 pass.ALL_COMMAND_FILESunchanged; the command distributes via the plugin bundle, not the curated standalone-installer set..mtssource changes; no.mjsregeneration beyond the command mirror.Test plan
/production-readiness-review #<pr>fans the four reviewers and returns one deduplicated, severity-ranked punch-list without editing codePart of the 2026-06-17 report-coverage build train; PR #246 (
/ship) is the fix-side sibling. No new dependencies.