gos-mission-control

Coordinate multi-agent Sales & Positioning workflows with predefined pipelines and human checkpoints.

41|27|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/kcleto-ai/growth-os-skills --skill gos-mission-control
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gos-mission-control
Source: https://github.com/kcleto-ai/growth-os-skills/tree/main/.claude/skills/gos-mission-control
Command: npx skills add https://github.com/kcleto-ai/growth-os-skills --skill gos-mission-control

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates a multi-agent Sales & Positioning workflow by receiving a structured briefing, validating cross-prerequisites, and orchestrating eight specialized employees as subagents to deliver client-facing results.

Core Features & Use Cases

  • Orchestration of an 8-employee squad (nicho-explorer, mapear-nicho, cliente-radar, lp-builder, gtm-architect, playbook-vendas, meeting-prep, pitch-deck-builder) with context isolation.
  • Handoff validation & retries: validates prerequisites via gos-validate-handoff, supports multi-step pipelines with up to two retries and human checkpoints.
  • Predefined pipelines: lp, deck, gtm, full-client, full-niche with clear routing and quality gates.
  • Observability & governance: event logs for each subagent invocation and consolidated pipeline summaries.

Quick Start

Provide a briefing to gos-mission-control with the required 4-field structure to start a relevant pipeline and let it orchestrate the 8 employees.

Frequently Asked Questions about gos-mission-control

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

FAQPage Schema
How do I orchestrate a multi-agent sales workflow with predefined pipelines?

Multi-agent sales orchestration is managed by providing a structured briefing to trigger predefined pipelines like lp, deck, gtm, full-client, or full-niche, which route tasks across specialized subagents with strict quality gates and context isolation.

What is handoff validation in a multi-agent positioning pipeline?

Handoff validation checks cross-prerequisites between subagents using gos-validate-handoff, ensuring that required context and inputs are met before passing tasks downstream, with support for up to two retries upon failure.

How do I add human checkpoints before delivering client-facing sales materials?

Human checkpoints are integrated directly into the custom pipeline composition flow, allowing you to pause and review outputs before any client-facing deliverables are finalized and released by the orchestrated subagents.

Can I compose a custom multi-agent flow instead of using predefined sales pipelines?

Custom multi-agent flows can be composed by chaining up to four serial employees from the eight-member squad, providing flexibility when the predefined lp, deck, gtm, full-client, or full-niche pipelines do not fit your specific use case.

How do I track subagent invocations and events during a sales orchestration pipeline?

Subagent invocations and pipeline events are tracked via built-in observability and governance features, generating event logs for each step and delivering a consolidated summary with actionable next steps upon completion.

Do I need a specific briefing format to start a multi-agent sales pipeline?

A structured briefing with a required four-field structure must be provided to start any relevant pipeline, ensuring the orchestrated squad has the necessary context to execute tasks and maintain proper context isolation.