install-departmentlisted

# Install Department Capture *how a department actually works* — tools, methodology, roles, cadence, taxonomy, automations, metrics — into a structured spec the company brain can index. The dept head leads; the skill orchestrates sub-agents that probe each connected tool in parallel. ## Quick start The head of the department being installed runs: ``` install-department --department <function> ``` Example: `install-department --department product`. The skill walks the head through five phases (Connect → Probe → Interview → Synthesize → Validate). Total time: 60–90 min, mostly background. The output is one markdown file (`department-spec.md`) plus one JSON manifest (`department.json`) written to the brain. ## What gets installed A **Department Spec** with seven canonical sections: | Section | What it captures | |---|---| | Tools | Inventory of tools the dept uses, with what data lives in each | | Roles | Who-does-what, distinguishing accountable vs consulted | | Cadence | Recurring meetings, reviews, cycles, deadlines | | Pipeline | The sequential stages work moves through (e.g. Signal → Opportunity → Solution → PRD → Delivery → Release for Product) | | Taxonomy | The categories/themes/tags the department classifies work by | | Automations | What runs without human intervention (cron jobs, webhooks, integrations) | | Metrics | What the dept reports on, and what thresholds matter | This format is canonical — the runtime indexes against these section names. Other downstr