What problem does it solve? Design documents often go straight to implementation without structured review, leading to missed security flaws, unclear use cases, and misaligned architecture that surface only after code is written. This skill enforces a mandatory multi-perspective review gate so complex features are validated by five specialist reviewers before any implementation starts. ## Core Features & Use Cases - Parallel Specialist Review: Spawns Product Manager, Architect, Designer, Security, and CTO agents simultaneously, each with a detailed checklist covering use cases, architecture, UX, OWASP threats, and TDD readiness. - Iterative Gate Protocol: Aggregates structured verdicts (APPROVED or NEEDS_REVISION), consolidates blockers and questions, and supports up to 3 revision cycles before escalating to a human decision. - Dual Coordination Modes: Works with fire-and-forget Task subagents by default, or persistent Team Mode teammates that retain context across review rounds when TeamCreate and SendMessage are available. - Use Case: After brainstorming produces docs/plans/2026-01-11-contact-assistant-design.md, the gate auto-activates, all five agents review it, security flags a userId trust-boundary blocker, and the design is revised and re-reviewed until all approve. ## Quick Start Ask the agent to run the design review gate on your design document, for example by saying: review the design at docs/plans/my-feature-design.md with all five reviewers.
