gsd-orchestrator

Orchestrate GSD subprocesses to automate end-to-end software builds.

Updated May 25, 2026
One-click install
npx skills add https://github.com/cmetech/otto-cli --skill gsd-orchestrator-cmetech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-orchestrator
Source: https://github.com/cmetech/otto-cli/tree/main/gsd-orchestrator
Command: npx skills add https://github.com/cmetech/otto-cli --skill gsd-orchestrator-cmetech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end software builds by orchestrating GSD as a subprocess controller that plans, codes, tests, and ships software from a spec.

Core Features & Use Cases

  • Autonomous build orchestration from spec to delivery with cost tracking and blocker resolution.
  • Real-time state inspection, step-wise control, and guided decision points for budgets and milestones.
  • Use Case: When asked to "build something" or "create a project," it orchestrates the workflow to deliver working software locally.

Quick Start

Run a milestone from a spec file and start an autonomous build with GSD headless using your spec as context and enable auto-build.

Frequently Asked Questions about gsd-orchestrator

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

FAQPage Schema
How do I automate software builds from a spec file end-to-end?

Automated software builds from a spec file are orchestrated by GSD as a subprocess controller, handling planning, coding, testing, and shipping entirely within your local environment. It manages milestone execution and state querying throughout the workflow.

Can I monitor build progress and handle blockers during an autonomous build?

Build progress monitoring and blocker handling are supported through real-time state inspection, step-wise control, and safe block handling mechanisms. The orchestrator provides guided decision points for budgets, milestones, and intervention routing commands.

What is the best way to track costs during an autonomous build workflow?

Cost tracking during an autonomous build workflow is handled natively through the orchestrator's cost reporting and budget management features. It provides guided decision points for milestones and budgets as your software is planned and shipped.

Does GSD orchestrator support running builds locally without external dependencies?

Local builds without external dependencies are fully supported, as the orchestrator runs GSD as a subprocess controller in your local environment. It requires no listed dependencies to plan, code, test, and ship software from a spec file.

How do I start an autonomous build using a spec file as context?

To start an autonomous build, run a milestone from your spec file using GSD headless mode with the spec as context, then enable auto-build. This initiates the end-to-end workflow from spec creation through final delivery.

When should I not use an autonomous build orchestrator for software delivery?

An autonomous build orchestrator is not ideal for software delivery when you need manual control over every coding step rather than milestone-based execution. It is designed for teams and individuals who want automated, spec-driven builds with cost tracking and blocker resolution.