/arnold:build
Build code guided by acceptance criteria in your docs.
When to use it
When you want Arnold to guide code construction directly from your documentation. Arnold reads your feature docs, identifies acceptance criteria, builds code to satisfy each one, and verifies with code citations.
Usage
> /arnold:build
🦕 ARNOLD BUILD
━━━━━━━━━━━━━━━
Reading docs/booking/ ...
Found 4 acceptance criteria to satisfy:
1. Users can browse available classes by date
2. Users can book a spot if capacity allows
3. Users cannot book the same class twice
4. Booking confirmation sent via email
Building...
✓ Criterion 1: browse classes
→ src/controllers/classes_controller.rb:12
✓ Criterion 2: book a spot
→ src/models/booking.rb:34
✓ Criterion 3: no duplicate bookings
→ src/models/booking.rb:8 (uniqueness validation)
✓ Criterion 4: confirmation email
→ src/mailers/booking_mailer.rb:5
✓ 4/4 criteria satisfied with code citations.
What it does
- Reads acceptance criteria from your feature docs
- Enumerates each criterion that needs to be satisfied
- Builds code to satisfy each one
- Verifies each criterion with a code citation (file path and line number)
- Reports which criteria passed and which need more work
💡 Tip
You don't have to use /arnold:build. Build code however you want, then use /arnold:check to verify alignment.
See also
- /arnold:check - Verify docs and code match
- /arnold:plan - Flesh out acceptance criteria before building