/arnold:decide
Record an architectural or product decision in your docs.
When to use it
When your team makes a decision that affects how a feature works. Arnold creates a decision record in docs/decisions/ and links it to the relevant features.
Usage
> /arnold:decide
🦕 ARNOLD DECISION LOG
━━━━━━━━━━━━━━━━━━━━━━
✓ DEC-001: Stripe for payments (accepted, 2026-03-15)
✓ DEC-002: No overbooking in v1 (accepted, 2026-03-16)
○ DEC-003: Google Calendar only, no Apple (pending, 2026-03-20)
To record a new decision, describe it and Arnold
will log it in docs/decisions/.
What it does
- Creates a decision record with an ID, title, status, and date
- Stores it in
docs/decisions/as a markdown file - Links the decision to the affected feature(s)
- Captures the reasoning so future contributors understand why
See also
- /arnold:status - See project overview including decisions
- /arnold:review - Review docs for missing decisions