drive-fleetlisted

# Drive Fleet A two-phase workflow for driving a fleet of MRs/PRs to done in parallel with a manager that never touches a working tree. Platform-neutral: all VCS/CI mechanics delegate to `/mr` and `/ci`. ## When to use **why-not-mechanizable:** skill workflow guidance; each step requires understanding the surrounding context (repo, task shape, prior state). - 2+ independent lanes / multiple MRs, often across sibling repos `(review-time: see section note)` - You want a hands-off MANAGER that delegates every edit and only stops when the whole fleet is done `(review-time: see section note)` - Not for single-MR work - use `/build` + `/mr` directly `(review-time: see section note)` ## The goal condition The built-in `/goal` command keeps the session working across turns until the condition holds, then auto-clears. Set it once, in the MANAGER session - it is session-scoped and resets on resume, so a re-planned session re-sets it. Template (fill the `{knobs}`): > Every open MR/PR from `{plan}` is CI-green, reviewed (`{review_depth}` applied via review-pr), and rebased on `{target_branch}`. `{post_completion_action}` | Knob | Default | | --- | --- | | `target_branch` | `main` | | `review_depth` | blockers + majors + one-line fixes | | `post_completion_action` | none (repo-specific; e.g. "Once all hold simultaneously, trigger the `notify_reviewers` job on each") | ## Phase 1 - Plan via grills 1. Run `/grill-with-docs` (add `grill-me` if you have it installed) to pressure-te