dept-save-statelisted

# dept-save-state Persists department state at end of session. Writes `dept-state.md` and `member-roster.md`. Called by Dept Heads before stopping. ## Usage ``` /dept-save-state [dept-slug] /dept-save-state content-creation /dept-save-state all ``` ## What It Writes ### dept-state.md Path: `~/.agency/agents/{dept}/state/dept-state.md` Key:value format, max 20 lines: ``` dept: {dept-name} head: {head-agent-name} last-updated: {YYYY-MM-DD HH:MM} active-coords: [DC names] | none active-pipelines: [pipeline names] | none open-issues: [issue slugs] | none blocked-on: [description or "none"] current-priority: {top D1 initiative or "none"} incoming-count: {n} | 0 notes: {freeform, max 2 lines} ``` ### member-roster.md Path: `~/.agency/agents/{dept}/state/member-roster.md` Per-member status: ``` | Member | Role | Status | Current Project | Utilization | |---|---|---|---|---| | {name} | {role} | available | none | 0% | ``` ### Session Log Appends to: `~/.agency/agents/{dept}/memory/sessions/YYYY-MM-DD.md` ### Decisions Appends any new decisions to: `~/.agency/agents/{dept}/memory/decisions.md` ## Steps 1. Read current `dept-state.md` (if exists) as baseline 2. Collect from Dept Head session: - Active DC names and D3 track states - Active pipelines - Open issues and blockers - Current priority - Any new decisions made this session 3. Write updated `dept-state.md` 4. Write updated `member-roster.md` 5. Append session log entry 6. Append any new decisions to `d