review
Analyze project architecture from multiple expert perspectives to identify actionable improvements and validate technical decisions.
Instructions
Multi-perspective architecture review. Analyzes full project context and produces actionable findings from expert viewpoints. Use focus parameter to zoom in on a specific feature, page, or decision. Use perspective_group to select a predefined group (technical/business/founder) instead of listing individual perspectives.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| perspectives | No | Which perspectives to include. Defaults to all nine. Overrides perspective_group if both are provided. | |
| perspective_group | No | Select a predefined group: technical (cto+security+devops), business (product+customer+strategy), founder (investor+unicorn_founder+solo_entrepreneur). Ignored if perspectives is specified. | |
| focus | No | Specific feature, page, module, or decision to focus the review on. E.g. "user login page", "payment integration", "should I use Supabase or Firebase", "what can I delete or simplify". The full project is still scanned for context, but findings focus on this area. | |
| customer_role | No | Description of target customer for the customer perspective. E.g. "a startup CTO evaluating CI tools" | |
| project_path | No | Path to the project to review. Defaults to current working directory. |