plan_review_skill

Overview

This skill coordinates multiple specialized reviewers to evaluate a plan in parallel. It runs independent review agents focused on architecture, Rails best practices, and code simplicity to provide a comprehensive assessment and actionable feedback. Results are aggregated into a concise summary with prioritized recommendations.

How this skill works

You supply a plan file path or paste the plan content. The skill dispatches three reviewers concurrently: a Rails architecture reviewer, a Rails implementation reviewer, and a code simplicity reviewer. Each agent returns findings, risks, and suggested changes, and the skill merges those outputs into a unified review with prioritized items and clear next steps.

When to use it

• Before starting implementation of a Rails feature or migration to validate design and assumptions.
• When you need fast, multi-perspective feedback on an implementation plan or technical proposal.
• To audit plans for maintainability, adherence to Rails conventions, and unnecessary complexity.
• When preparing design documents for peer review or stakeholder approval.
• To catch architectural risks and code smells early in planning.

Best practices

• Provide the full plan text or a precise file path and include relevant context (schema, dependencies, constraints).
• Highlight critical sections or decisions you want focused review on to get targeted feedback.
• Keep plans under practical size limits or split very large plans into focused parts for separate reviews.
• Review aggregated recommendations and prioritize fixes by risk and implementation effort.
• Iterate: run the reviewers again after addressing major recommendations to confirm improvements.

Example use cases

• Validating a migration plan that touches database schema, background jobs, and deployment strategy.
• Reviewing a feature specification to ensure it follows Rails conventions and avoids over-complex patterns.
• Assessing a refactor plan to identify risks to existing behavior and opportunities to simplify code.
• Preparing a technical proposal for engineering leadership with a summary of risks and mitigation steps.
• Rapidly getting multi-angle feedback on onboarding tasks or architectural decisions.