admiral

Orchestrate design, build, review, and Azure provisioning pipelines with validated handoffs.

9|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/TykoDev/SupremeTeam --skill admiral
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: admiral
Source: https://github.com/TykoDev/SupremeTeam/tree/main/skills/admiral
Command: npx skills add https://github.com/TykoDev/SupremeTeam --skill admiral

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Eliminate fragmented, single-pass AI attempts by providing a single, proactive orchestrator that drives design, build, review, and optional Azure provisioning through validated handoffs and persistent saves to ensure traceability and resumeability.

Core Features & Use Cases

  • Unified Orchestration: Route user requests through design (commander), build (build-management), review (code-chief), and optional Azure provisioning (azure-provisioner) with a single entry point.
  • Gatekeeper-Mediated Handoffs: Enforce cross-pipeline validation using gatekeeper-admiral with deterministic submission_id, max revision cycles, and clear escalation paths.
  • Persistence & Resume: Create and manage skillset-saves run directories, _state.md and _lock.md, and support resume, idempotency, and degradation tiers when context or saves are constrained.
  • Adaptive Partial Pipelines: Run full pipelines, subsets, or standalone sub-orchestrators while writing skip records and standalone context for safe downstream assumptions.

Quick Start

Ask admiral to "run the full pipeline for a REST API task manager, include Azure deployment, and persist progress for resume."

Frequently Asked Questions about admiral

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

FAQPage Schema
How do I orchestrate end-to-end software delivery pipelines with Azure provisioning?

Cross-pipeline consistency checks enforce deterministic submission IDs, maximum revision cycles, and clear escalation paths using gatekeeper-mediated validation. Adversarial gatekeeper validation ensures idempotent handoffs and clear escalation paths during software delivery.

Can I resume a partially completed software pipeline if the context or saves are constrained?

Yes, partially completed software pipelines can be resumed using run directories, state files, and lock files. The orchestration supports resume, idempotency, and degradation tiers when context or saves are constrained during execution.

How do I run partial pipelines for specific stages like design or code review without the full lifecycle?

Partial pipelines for specific stages are executed by running subsets or standalone sub-orchestrators while writing skip records and standalone context. This ensures safe downstream assumptions for design, build, or code review stages without the full lifecycle.

Do I need Azure dependencies to use this software orchestration approach?

No, Azure dependencies are not required as Azure provisioning is an optional stage within the orchestration. The core orchestration handles design, build, and code review stages independently of any Azure deployment requirements.