autospec-fleet

Supervise autospec execution across GitHub repositories with queue summaries.

3|1|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/berlinguyinca/autospec --skill autospec-fleet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autospec-fleet
Source: https://github.com/berlinguyinca/autospec/tree/main/skills/autospec-fleet
Command: npx skills add https://github.com/berlinguyinca/autospec --skill autospec-fleet

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires curl, git, gh, jq, yq, ajv, bash, and includes scripts (resource) components.

What problem does it solve?

Coordinating reliable, repeatable AI-driven implementation across multiple GitHub repositories is hard to manage consistently, leaving you with unclear progress, unvalidated changes, and poor operational control.

Core Features & Use Cases

  • Fleet orchestration: initializes an empty workspace, accepts multiple GitHub repository URLs, and orchestrates repo-level /autospec-run workers.
  • Config and scheduling controls: validates fleet configuration, applies per-repo profile selection, and respects node-local capacity for parallelism.
  • Operational visibility and control: summarizes queue state across repos and forwards stop semantics to active repo workers.

Quick Start

Ask your agent to run fleet initialization and then launch workers with: /autospec-fleet init https://github.com/org/repo-a.git https://github.com/org/repo-b.git && /autospec-fleet run --profile qwen3-32b-laptop.

Frequently Asked Questions about autospec-fleet

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I orchestrate AI-driven implementation across multiple GitHub repositories?

Orchestrating AI-driven implementation across multiple GitHub repositories requires a centralized fleet manager to initialize a workspace, validate configs, and schedule per-repo workers. This skill coordinates repo-level execution, summarizes queue state, and forwards stop controls to active workers.

How do I validate fleet configuration files for multi-repo workflow orchestration?

Fleet configuration validation is handled by linting YAML configs against JSON schemas using ajv and yq. This ensures deterministic setup before scheduling per-repo commands, preventing unvalidated changes and poor operational control across the repository queue.

Do I need GitHub CLI and jq installed to run multi-repo worker scheduling?

Yes, you need GitHub CLI (gh), jq, yq, ajv, curl, git, and bash installed. These dependencies normalize repo URLs, validate YAML configurations, schedule commands, and emit JSON or human-readable queue summaries for the orchestrated monitors.

Can I monitor run status and forward stop commands to active repo workers?

Monitoring run status and forwarding stop semantics to active repo workers is supported. The tool summarizes queue state across repositories, providing operational visibility and control over the orchestrated execution monitors.

What is the best way to bootstrap a workspace for fleet-wide autospec execution?

Bootstrapping a workspace for fleet-wide autospec execution involves initializing an empty directory and passing multiple GitHub repository URLs. The tool then applies per-repo profile selection, respects node-local capacity, and launches the scheduled workers.