/arnold:review
Doc critique across usability, product, and technical lenses.
When to use it
When you want Arnold to review your docs for quality, not just alignment. Arnold reads your docs through three different lenses and flags issues like missing policies, undefined error handling, or accessibility gaps.
Usage
> /arnold:review
🦕 ARNOLD DOC REVIEW
━━━━━━━━━━━━━━━━━━━━
Reviewing docs across 3 lenses...
📐 Product lens:
⚠ Cancellation policy not documented anywhere
⚠ Waitlist behavior undefined
🔧 Technical lens:
✓ API contracts well-defined
⚠ No error handling docs for payment failures
👤 Usability lens:
✓ User flows are clear and complete
⚠ No accessibility requirements documented
4 issues found across 3 lenses.
What it does
- Product lens - Are business rules and policies documented? Missing cancellation policy, undefined pricing tiers, etc.
- Technical lens - Are API contracts, error handling, and system constraints documented?
- Usability lens - Are user flows clear? Are accessibility and edge case scenarios covered?
See also
- /arnold:plan - Generate docs for gaps found in review
- /arnold:feature - Completeness matrix