ainb-fleet:sequence
Ordered multi-step prompts to fleet targets, ack-gated between steps via JSONL assistant-turn-end detection. Use for cycles like disconnect→reconnect→verify, or any flow where step N+1 requires step N to have completed first. The skill BLOCKS until each target's transcript shows the next assistant turn finishing OR per-step timeout fires (default 300s).
Best use case
ainb-fleet:sequence is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Ordered multi-step prompts to fleet targets, ack-gated between steps via JSONL assistant-turn-end detection. Use for cycles like disconnect→reconnect→verify, or any flow where step N+1 requires step N to have completed first. The skill BLOCKS until each target's transcript shows the next assistant turn finishing OR per-step timeout fires (default 300s).
Teams using ainb-fleet:sequence should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/sequence/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How ainb-fleet:sequence Compares
| Feature / Agent | ainb-fleet:sequence | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Ordered multi-step prompts to fleet targets, ack-gated between steps via JSONL assistant-turn-end detection. Use for cycles like disconnect→reconnect→verify, or any flow where step N+1 requires step N to have completed first. The skill BLOCKS until each target's transcript shows the next assistant turn finishing OR per-step timeout fires (default 300s).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# ainb fleet:sequence
Send N prompts in order. Between steps, wait for every target's next
assistant-turn-end before firing the next step.
## Run
```bash
ainb fleet sequence "step1" "step2" "step3" --all --timeout 300
```
## Args
| arg/flag | purpose |
|---|---|
| `<steps...>` | 1 or more prompts, fired in argv order |
| `--all` | required (v0.1 only supports --all targeting) |
| `--timeout <seconds>` | per-step ack deadline, default 300 |
## How ack-gating works
After each step (except the last):
```
for each target:
watch ~/.claude/projects/<cwd-slug>/<sid>.jsonl via notify
resolve when next row has:
type == "assistant"
message.stop_reason == "end_turn"
OR timeout fires
```
This guarantees claude has *finished responding* to step N before step
N+1 lands. The watch runs in parallel across all targets; the next step
fires when all targets either acked or timed out.
## Common flows
**Disconnect → reconnect cycle:**
```bash
ainb fleet sequence \
"remote-control disconnect" \
"remote-control" \
--all
```
**Clear → resume:**
```bash
ainb fleet sequence \
"/clear" \
"continue from where you left off" \
--all
```
**Verify-then-act:**
```bash
ainb fleet sequence \
"/status" \
"if status shows clean, proceed; otherwise abort" \
--all
```
## Caveats
- **--all only in v0.1.** Filter/cwd selectors not yet wired for sequence.
Workaround: use a wrapper script that builds a filter list then runs
per-target sequences.
- **Ack detection requires JSONL access.** If `~/.claude/projects/` is
unreadable (perms / sandboxing), ack always times out → step N+1
fires after the timeout regardless of actual completion.
- **Default 300s is generous.** For chatty steps (analysis prompts, code
generation), 300s is realistic. For trivial prompts (`/clear`), pass
`--timeout 30` to fail fast.
- **Tail wallclock = sum of per-step wallclocks.** A 3-step sequence
against a slow model can take minutes. Daemon mode keeps moving;
sequence is intentionally synchronous.
## Verify ack-gating actually happened
Time the run:
```bash
time ainb fleet sequence "say hi" "say bye" --all --timeout 30
```
If elapsed is suspiciously short (< number of round-trips × ~3s), check
the JSONL transcripts to see if turn-ends were actually observed —
fall-through on timeout looks identical from the outside.Related Skills
test-ainb
Run tests for the ainb (agents-in-a-box) Rust workspace via a 5-layer strategy — unit, insta snapshot, mock-plugin compositing, real-plugin spawn, vhs recording. Wraps cargo + insta + vhs into one CLI. Use when Stevie says "/test-ainb", "test ainb", "run ainb tests", "snapshot <component>", "regenerate vhs tapes", or any phrasing about validating ainb test layers. The skill autodetects which ainb-tui worktree the cwd sits in and dispatches to scripts/run.sh.
ainb-fleet:standup
Show fleet status — every claude session running on the host, merged across ainb + claude-peers broker + background jobs. Use when you need to enumerate sessions before composing an action, see which sessions have a peer registered (broker-routable) vs tmux-only, check the `summary` of each session, or pipe the list into jq for filtering. Default output: text table. Pass --format json for LLM consumption.
ainb-fleet:needs
Center control panel — enumerate every claude session that is blocked waiting on something: a user answer (AskUserQuestion fired), an API error retry, an idle assistant turn-end with no follow-up, or an explicit WAITING: marker. Returns rich JSON with signal kind + context per session. Use this when you've stepped away from the fleet and want one place to see everything that wants your attention and answer it.
ainb-fleet:fleet-needs
Workflow-backed Jarvis control panel. Runs the deterministic `hangar` workflow with verb=needs (discover → enrich → prioritize), renders the Jarvis HUD from its render-ready cards, fires AskUserQuestion per blocked session, and routes each answer back via tmux send-keys (broker fallback only). Requires the workflow gate (CLAUDE_CODE_WORKFLOWS=1). If the gate is off, fall back to the prompt-driven `/ainb-fleet:needs` skill.
ainb-fleet:daemon
Long-running watcher that scans every claude session every 5s and auto-sends `continue` to any session whose recent tmux pane buffer matches a known API-error regex (rate_limited, overloaded_error, internal_server_error, request_timeout, socket_hang_up, fetch_failed, ECONNRESET). Use this when you want unattended recovery from transient API failures across the fleet.
ainb-fleet:broadcast
Fan out a single prompt to selected claude sessions across the fleet. Use when you need to apply the same instruction (e.g. `/clear`, `git pull`, `remote-control disconnect`) to many sessions at once. Routing: peers-first (broker HTTP) when peer registered, tmux send-keys fallback otherwise. Refuses to run without an explicit targeting flag (--all, --filter <regex>, or --cwd <substring>) — no implicit fan-out.
ainb-fleet
Fleet orchestration overview — the `ainb fleet ...` Rust subcommand namespace for driving every claude session on the host. Routes to one of five sub-skills (standup / broadcast / sequence / needs / daemon). Invoke this for an at-a-glance map of what fleet can do; reach for the specific sub-skill for the verb you want.
workflow
Guide through structured delivery workflow with plan, implement, validate phases
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
validate
Verify implementation against specifications
ui-ux-pro-max
UI/UX design intelligence. 67 styles, 96 palettes, 57 font pairings, 25 charts, 13 stacks (React, Next.js, Vue, Svelte, Astro, Nuxt, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, Jetpack Compose). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.
tui-style-guide
TUI style guide for consistent terminal interface design