# Marshal

Meta-orchestrator that takes any direction, broad, specific, or vague, and...

- Repository: https://github.com/SethGammon/Citadel (927 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-10-30
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add SethGammon/Citadel --skill marshal -g -a claude-code -y`
Codex: `npx skills add SethGammon/Citadel --skill marshal -g -a codex -y`
Cursor: `npx skills add SethGammon/Citadel --skill marshal -g -a cursor -y`
Gemini CLI: `npx skills add SethGammon/Citadel --skill marshal -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add SethGammon/Citadel`

## Description

Meta-orchestrator that takes any direction, broad, specific, or vague, and autonomously chains skills and context into actionable work. Gathers context from codebase, docs, and memory. Only asks the user when it genuinely cannot proceed. Single-session orchestrator.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# /marshal, Session Commander

## Orientation

Use Marshal when the task is:
- Multi-step but bounded (completable in one session)
- Needs investigation before action
- Spans multiple skills but doesn't need campaign persistence
- Too complex for a single skill but doesn't need Archon/Fleet

**Don't use when:** the task spans multiple sessions (use /archon); work decomposes into 3+ parallel streams (use /fleet); you only need research with no action (use /research).
- Parallel execution (use Fleet)

## Commands

| Command | Behavior |
|---|---|
| `/marshal [direction]` | Full loop: understand → plan → execute → report |
| `/marshal assess [area]` | Read-only: understand the area, produce findings, don't fix |

## Protocol

### Phase 1: UNDERSTAND

Parse the user's direction into structured intent:

1. Read AGENTS.md, then CLAUDE.md if present, to understand the project's architecture and conventions
2. Identify: scope (which files/directories), perspective (user, developer, admin),
   mode (audit, fix, build, improve, map), depth (surface scan vs deep investigation)
3. If the direction is ambiguous, make a reasonable interpretation and state it.
   Do NOT ask clarifying questions unless genuinely stuck.

### Phase 2: PLAN CHAIN

Map the intent to a sequence of actions:

| Direction Pattern | Chain |
|---|---|
| "audit [area]" | explore → analyze → report findings |
| "fix [thing]" | investigate root cause → fix → verify → report |
| "map [area]" | read files in parallel → synthesize → produce analysis |
| "improve [area]" | audit current state → identify gaps → implement → verify |
| "what should [X] be" | research → analyze options → recommend with reasoning |
| "research [topic]" | search codebase + web → synthesize → report |

Announce the chain before executing: "I'll [step 1], then [step 2], then [step 3]."

### Phase 3: EXECUTE

For each step in the chain:

The rest: https://github.com/SethGammon/Citadel/blob/HEAD/skills/marshal/SKILL.md