backend-launcher

Solid

Use when Compound V's dispatcher needs to run one file-scoped job on a chosen backend (Claude subagent, headless Codex worker, headless Antigravity worker, headless Cursor worker, headless Devin worker, or headless opencode worker) and get back a canonical job_result. The single job_spec → job_result contract every adapter implements; the orchestrator speaks only this contract and never sees backend-specific flags.

API & Backend 38 stars 5 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 82/100

Stars 20%
53
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Backend Launcher > *"Same syringe, different supes. The dispatcher doesn't care who's holding it — it cares what comes back."* A reusable sub-skill (a sibling directory under `skills/`, pulled in by prose "read this file and apply"). It exposes **one contract**. The orchestrator hands a `job_spec` to whichever adapter the manifest's `backend` names, and gets back a canonical `job_result` — identical shape across every backend. Enforcement is uniform because it lives in the *caller's* scope gate, not in the backend. There is no skill-import API: an adapter is a sibling doc (`adapter-codex.md`, `adapter-claude.md`, `adapter-antigravity.md`) that says "read the contract in this file, then do the backend-specific steps." Adapters are built by downstream tasks; this file is the contract they implement. --- ## The contract ### INPUT — `job_spec` ```jsonc { "backend": "codex", // claude | codex | antigravity | cursor | devin | opencode "prompt": "…", // the worker prompt (opens with the planner/executor lock, below) "tier": "standard", // frontier | deep | standard | light — the routing INTENT (stable across model churn) "effort": "medium", // low | medium | high | xhigh — orthogonal reasoning-effort hint (optional; xhigh is codex-only) "model": "gpt-5.6-sol", // OPTIONAL explicit override; when present it skips resolution. // executio...

Details

Author
procoders
Repository
procoders/superpowers-v
Created
4 months ago
Last Updated
yesterday
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

API & Backend Listed

backend-developer

⚠️ Backend specialist for Solaris. Laravel/PHP, Node (Express/Fastify/NestJS), Python (FastAPI/Django), .NET (ASP.NET Core), Rails. API design (REST + GraphQL), authentication, database (Postgres/MySQL), background jobs + sagas, file storage, payments, webhooks, spec→code implementation. Fires on any server-side work - APIs, business logic, data persistence, auth flows, queues, integrations, "design an API", "add a background job", "review this API PR", "implement this spec". Routes to frontend-developer for UI, fullstack-developer for cross-stack, devops-engineer for deployment, database-administrator for schema-at-scale, security-auditor for security review.

1 Updated today
Shaisolaris
AI & Automation Listed

arbeitsplan-backend

Decides whether a compiled arbeitsplan run executes in-session, as a headless matrix of fresh claude -p processes, or inside the Workflow tool, and emits the checked backend object workflow.json requires. Use when the user asks whether to run something as a workflow or a matrix, whether a job should run in parallel agents or in this session, or why a run had to be forced into one. Recommend-only. For which pattern fits, hand off to arbeitsplan-patterns; for which of the four approved workflows applies, to arbeitsplan-start.

1 Updated today
Anselmoo
AI & Automation Listed

async-job-orchestration

Manage long-running async LLM jobs across Claude, Codex, Gemini, Grok, Mistral, Devin, and Cursor. Use for parallel or non-blocking execution. Covers backend-qualified durability, cache-aware `promptParts`, `cache-state://` MCP resources, and the Claude `cache_ttl_expiring_soon` warning.

16 Updated 5 days ago
verivus-oss