fleet

Orchestrate multi-wave campaigns with non-overlapping workstreams and persist state under .citadel/fleet/.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/special-place-administrator/citadel_codex --skill fleet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fleet
Source: https://github.com/special-place-administrator/citadel_codex/tree/main/skills/fleet
Command: npx skills add https://github.com/special-place-administrator/citadel_codex --skill fleet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Parallel campaign coordination by partitioning work into non-overlapping waves and persisting state to .citadel/fleet/. This approach prevents same-wave collisions while enabling discoveries to be shared across waves.

Core Features & Use Cases

  • Coordinate multiple parallel workstreams without overlapping within the same wave.
  • Share discoveries between waves and persist fleet state under .citadel/fleet/.
  • Orchestrate wave progress, aggregate outputs, and prepare handoff data for the next wave.
  • Use Case: large feature initiatives that can be split into independent subsystems to accelerate delivery.

Quick Start

Define wave scopes and run the fleet workflow to orchestrate waves and capture handoff data.

Frequently Asked Questions about fleet

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

FAQPage Schema
How do I coordinate parallel work streams without collisions in large projects?

Coordinate parallel work streams by partitioning large projects into non-overlapping waves, ensuring independent scopes execute concurrently while state is persisted under .citadel/fleet/ for auditability.

What is wave-based execution for multi-wave campaign orchestration?

Wave-based orchestration enforces a protocol where independent work streams run in non-overlapping scopes, aggregating outputs and preparing handoff data to share discoveries across subsequent waves for multi-wave campaigns.

How do I track progress and share state across multiple parallel workstreams?

Track progress and share state across parallel workstreams by persisting fleet state under .citadel/fleet/, orchestrating wave progression, and capturing handoff data that shares discoveries for the next wave.

Can I use wave orchestration for large feature initiatives split into independent subsystems?

Wave orchestration suits large feature initiatives decomposed into independent subsystems, accelerating delivery by coordinating non-overlapping scopes and sharing cross-wave discoveries to maintain progress.

When should I not use wave-based parallel campaign coordination?

Avoid wave-based parallel campaign coordination for projects that cannot be decomposed into non-overlapping scopes or lack cross-wave discovery sharing requirements, as it enforces a strict wave execution protocol.