/arnold:plan
Flesh out feature docs with flows, edge cases, and acceptance criteria.
When to use it
After /arnold:init has scaffolded your docs, use /arnold:plan to fill in the gaps. Arnold analyzes each feature folder and generates missing documentation like flow descriptions, edge cases, and acceptance criteria.
Usage
> /arnold:plan
🦕 ARNOLD GAP ANALYSIS
━━━━━━━━━━━━━━━━━━━━━━
Scanning feature docs for completeness...
auth: needs edge case docs (password reset, lockout)
booking: needs edge case docs (cancellation, waitlist)
payments: ✓ complete
calendar-sync: needs flow docs, edge cases, acceptance criteria
accounts: ✓ complete
3 features need work. Generating doc templates...
+ auth/auth-edge-cases.md (created)
+ booking/booking-edge-cases.md (created)
+ calendar-sync/calendar-flows.md (created)
+ calendar-sync/calendar-edge-cases.md (created)
+ calendar-sync/calendar-criteria.md (created)
✓ 5 new doc files created. Review and fill in the details.
What it does
- Scans each feature folder for completeness (overview, flows, edge cases, criteria)
- Identifies which doc types are missing per feature
- Generates templates for missing docs with starter content
- Reports what was created so you can review and refine
See also
- /arnold:init - Scaffold the initial docs structure
- /arnold:feature - See completeness matrix
- /arnold:check - Check alignment after planning