orchestration

Plugin orchestration from marketplace broomva-skills in broomva/skills. Commands read from the repo's manifest — yesterday.

Skills (14)

• arc

  Use when the user is handing over an unattended run and will not be there to answer: they are going to bed, stepping away, or leaving it overnight, and they want the work carried to an end state that is both finished and clean rather than to a stopping point. Symptoms: "I'm off until morning", "nobo

• autonomous

  Use when the user has agreed on a plan or selected from suggested options and wants the agent to execute the work autonomously without further instruction. Also use when the user issues a bare directive ("go", "proceed", "build X", "fix Y", "ship it", "be autonomous", "merge autonomously", "automerg

• ctx-core

  The shared context core, phase 1: a read-only shared board for every Claude Code session in a workspace scope. Hooks publish each session's start, the keyword of its ARC-STATUS line at every Stop, and its death on StopFailure to one append-only log per scope, as structured fields only. A SessionStar

• eve-forge

  Forge a personalized eve agent for a business end-to-end — absorb the business's artifacts, author the eve agent/ dir, validate, deploy to Vercel (or a VPS), smoke-test against ground truth, register, and evolve. The deterministic core is three safety gates distilled from a driven benchmark (BRO-167

• fleet-reconcile

  Deprecated alias of the fleet skill (renamed in fleet 0.6.0, BRO-3122; removed after one release). Use fleet; its reconcile workflow is this skill's old content.

• fleet

  The Broomva fleet: every Claude Code and Paseo session, PR and loop the coordinators drive, and the workflows that manage it. reconcile is the hourly launchd tick (observe, classify, report, owner asks; act under dry run). census, close-out and rollover are the coordinator's procedures from bstack's

• governed-autonomy-loop

  Turn any work-queue + any enforcement pipeline into a self-driving, self-healing, human-minimal autonomy loop with a control-systems safety envelope. A prose-defined governor closes a feedback loop over the queue, drives isolated worktree arcs to Done, is metacognitive (defers when the runtime can't

• handback

  Terminal-message contract for an autonomous arc that has run out of agent-executable work and genuinely needs a human. Produces a WORK ORDER — asks first, each one an imperative addressed to the reader, carrying a default so silence is never fatal (the exception is narrow and must be named: irrevers

• handoff

  Fresh-session handoff doc drafting. Produces a stable, single-file human-readable narrative state for the NEXT agent context (fresh session, after `/clear`, after persist iteration, after a tab close). The artifact lives at `docs/handoffs/YYYY-MM-DD-<arc>.md` and follows a stable shape: TL;DR + Stat

• p9

  Something is running and you are stuck waiting on it — CI checks on a PR you just pushed, a deploy going out, a container image build, a slow migration or a long reindex. This skill puts a watcher on the wait and spends the wait on the next piece of work, instead of watching a spinner or calling `sl

• persist

  bstack P12 — Persistent Loop Discipline. Cross-context restart loop where state lives in the filesystem (PROMPT.md + git tree + state.jsonl), not in the conversation. Each iteration spawns a fresh agent context. Solves the failure mode where work that must outlive one session loses its state when th

• provider-manager

  Subscription account manager for macOS (Claude Code CLI, OpenAI Codex CLI, Antigravity ACP, Orca, Keychain): account discovery, usage telemetry (Grok too, read-only), machine-wide balancer that fails over without killing running sessions, safe switching, and browser-session re-login. Use when: inspe

• resume

  Restore an arc that was killed mid-flight by something external — API 529 / 500, ENOTFOUND, ConnectionRefused, an expired login, a laptop that slept, a Ctrl-C. The operator restarts, types `resume`, and means *continue as though nothing had stopped you*: same arc, same plan, subagents and workflows

• role-x

  bstack P17 — Lens-Routed Request Articulation. The typed routing layer above P5 parallel-agent dispatch. On every substantive user input, the first-touch agent reflexively selects role lens(es) from `roles/<name>.md`, loads substantive context (files, conventions, domain checklists), and decides sin

Similar plugins