gsd-headless

Automate OTTO project milestones and workflow execution via headless CLI.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

OTTO teams need to run project orchestration and milestone workflows without a graphical UI. This skill enables headless control of OTTO projects via the CLI, automating milestone creation, workflow execution, and status monitoring while keeping governance intact.

Core Features & Use Cases

  • Headless orchestration of OTTO projects from specs to milestones and automated execution.
  • Create milestones from specs, run queued work, monitor progress, and steer or pause execution.
  • Supports multi-session workflows with file-based state and references material for extended guidance.

Quick Start

Run headless workflows with gsd headless to create milestones, auto-run queued work, and manage execution.

Frequently Asked Questions about gsd-headless

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

FAQPage Schema
How do I automate OTTO project orchestration and execute milestones from the CLI?

Headless OTTO project orchestration automates milestone creation, executes queued workflows, and monitors progress directly from the CLI. It uses a headless RPC-style workflow to run end-to-end development pipelines without a graphical UI.

How does headless workflow execution manage state across multiple sessions?

Headless workflow execution manages state using file-based storage in .otto/workflow and JSONL event streams. This approach coordinates multiple workers and tracks status changes across milestones for continuous pipeline operation.

Can I monitor and steer execution progress for queued work without a UI?

Yes, you can monitor progress, steer execution, and pause queued work without a UI. The headless CLI applies a references-driven knowledge base to coordinate tasks and respond to status changes across milestones.

What is the best way to create milestones from specs in a headless development pipeline?

Creating milestones from specs in a headless pipeline involves running the gsd headless CLI command. This automatically parses specifications, generates milestones, and queues work for automated execution across coordinated workers.

Do I need a graphical interface to coordinate multiple workers in an OTTO project?

No, you do not need a graphical interface to coordinate multiple workers. The headless orchestration workflow supports multi-session execution using file-based state and JSONL event streams to synchronize tasks.

Are there limitations when running headless RPC-style workflows for project orchestration?

Headless RPC-style workflows rely on file-based state in .otto/workflow and JSONL event streams, meaning execution depends on local filesystem access. Governance is maintained without a UI, but requires CLI availability.