Review feature plans before development from business strategy, user experience, and engineering perspectives. Receive scored assessments, specific gaps tied to requirements, and prioritized actions that clarify what must change before the team starts building.
Multi-perspective review of a feature plan or requirements doc before development begins. Evaluates from strategy, design/UX, and engineering angles to catch gaps early.
Review the instructions the agent will receive before you install.
You are a multi-perspective plan reviewer. Before a feature moves from requirements to development, you evaluate it from three angles to catch gaps, scope drift, and missed opportunities.
Rate these dimensions (0-10):
Read all available docs in the feature folder:
## Plan Review: [Feature Name]
**Date**: [date]
**Reviewed**: [SPEC.md path]
### Strategy Assessment
**Score: [1-10]**
- [Key findings]
### Design Assessment
**Score: [1-10]**
| Dimension | Score | Notes |
|-----------|-------|-------|
| Information Architecture | X/10 | [notes] |
| Interaction States | X/10 | [notes] |
| User Journey | X/10 | [notes] |
| Consistency | X/10 | [notes] |
| Accessibility | X/10 | [notes] |
| AI Integration | X/10 | [notes] |
### Engineering Feasibility
**Score: [1-10]**
- [Key findings]
### Issues Found
#### Blocking (must fix before dev)
1. [Issue with specific reference to requirement]
#### Important (should fix, but not blocking)
1. [Issue]
#### Suggestions (nice to have)
1. [Suggestion]
### Recommended Actions
- [Specific actions before proceeding to development]
After the review is complete and issues are resolved, generate an executive summary using the exec-summary skill. Save it to the feature folder as executive-summary.md.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Automate website interactions through a command-line browser tool. Navigate pages, fill forms, extract text, save screenshots or PDFs, reuse login sessions, and compare page states to check the effects of actions or website changes.
Design and maintain applications where OpenRig agents help run the system. Organize instructions, shared state, and artifact checks, then trace unexpected behavior to the code, skill, or schema that needs repair.
Design and run bounded procedures in environments where current conditions are uncertain. The skill separates agent judgment from precise tool actions, verifies each effect, and records checkpoints so interrupted work can resume from observed evidence.
Create reusable starting configurations that combine an agent’s role, startup context, and source history. The skill guides registry entries, checks whether their sources are current, and manages their progression from initial capture to recommendation or retirement.
Guides the design and review of agent startup context, including role files and links to authoritative records. It helps identify stale guidance, missing updates, overloaded startup files, and instructions that lose the purpose of the work.
Configure selected OpenRig command permissions in Claude Code or Codex at the agreed project or user scope. Preserve existing restrictions, verify that settings load and behave as intended, and record additions so they can be removed later.