sync

name	sync
description	Mid-week cross-department sync. Collects status from all departments, routes intelligence signals, identifies blockers, produces Chairman summary. Wednesday afternoon. Octopus colors: Purple (orchestration).

/sync: Cross-Department Sync

Octopus Colors: Purple (Manager)

Process

1. Read .chairman/config.json for active departments
2. For each department, scan:
   • departments/{dept}/knowledge/ for recent updates
   • .chairman/assignments/ for active assignments in that department
   • Any intelligence signals produced since last sync
3. Compile status per department:
   • What is complete since last sync
   • What is in progress
   • What is blocked (and why)
4. Route intelligence signals:
   • If Commercial learned something Operations needs, flag it
   • If Marketing data could help Commercial, flag it
5. Produce Chairman summary

Output Format

# Cross-Department Sync: [Date]

## Department Status
### [Department Name]
- Completed: [list]
- In Progress: [list]
- Blocked: [item] - needs [what] from [whom]

## Intelligence Routes
- [Source dept] > [Target dept]: [Signal summary]

## Decisions Needed
1. [Decision]: [Context, options, recommendation]
2. ...

## Suggested Actions
- [Next skill to run based on findings]

Rules

• Keep it to one page. The Chairman should read this in under 10 minutes.
• Only flag genuine blockers, not normal work-in-progress.
• Save to .chairman/reports/sync-YYYY-MM-DD.md
• Update .chairman/state.json with current assignment counts.