marshal

1# /marshal — Session Commander
2 
3## Orientation
4 
5Use Marshal when the task is:
6- Multi-step but bounded (completable in one session)
7- Needs investigation before action
8- Spans multiple skills but doesn't need campaign persistence
9- Too complex for a single skill but doesn't need Archon/Fleet
10 
11**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).
12- Parallel execution (use Fleet)
13 
14## Commands
15 
16| Command | Behavior |
17|---|---|
18| `/marshal [direction]` | Full loop: understand → plan → execute → report |
19| `/marshal assess [area]` | Read-only: understand the area, produce findings, don't fix |
20 
21## Protocol
22 
23### Phase 1: UNDERSTAND
24 
25Parse the user's direction into structured intent:
26 
271. Read AGENTS.md, then CLAUDE.md if present, to understand the project's architecture and conventions
282. Identify: scope (which files/directories), perspective (user, developer, admin),
29   mode (audit, fix, build, improve, map), depth (surface scan vs deep investigation)
303. If the direction is ambiguous, make a reasonable interpretation and state it.
31   Do NOT ask clarifying questions unless genuinely stuck.
32 
33### Phase 2: PLAN CHAIN
34 
35Map the intent to a sequence of actions:
36 
37| Direction Pattern | Chain |
38|---|---|
39| "audit [area]" | explore → analyze → report findings |
40| "fix [thing]" | investigate root cause → fix → verify → report |
41…