[FEATURE] /loop fire — trigger a scheduled loop cycle on demand

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

When running long autonomous development loops with /loop, I often need to trigger the next cycle immediately rather than waiting for the interval timer. My workflow uses /loop 20m with multiple agents on parallel git worktrees, where one agent's output unblocks the others. When I see Agent A finish a phase, I want to immediately kick Agents B and C into their next cycle instead of waiting up to 20 minutes for the cron to fire.

The current workaround is manually pasting the full loop prompt into the session, which works but defeats the purpose of having a scheduled loop and is error-prone with long prompts.

Proposed Solution

Add a /loop fire (or /loop now) command that immediately triggers the next execution of the active scheduled loop, without resetting the interval timer. The regular schedule continues unchanged after the manual fire.

Optionally, /loop fire <job_id> if multiple loops are active.

Alternative Solutions

1. Pasting the prompt manually — works but clunky with long prompts and easy to diverge from the scheduled version.
2. Shortening the loop interval — wastes API credits on unnecessary polling cycles.
3. Canceling and recreating the loop — loses the job ID and resets the expiration timer.

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_