Marshal
Meta-orchestrator that takes any direction, broad, specific, or vague, and...
Install
npx skills add SethGammon/Citadel --skill marshal -g -a claude-code -y- Repository
- SethGammon/Citadel927
- Category
- Engineering
- Updated
- 5d ago
- License
- MIT
- Context cost
- Lightabout 1,336 tokens
- Runs scripts
- No, instructions only
What it does
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.
/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:
- Read AGENTS.md, then CLAUDE.md if present, to understand the project's architecture and conventions
- Identify: scope (which files/directories), perspective (user, developer, admin), mode (audit, fix, build, improve, map), depth (surface scan vs deep investigation)
- 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:
