godmode-departments

name	godmode-departments
description	Route cross-domain Codex work through bounded advisory specialists with frozen ownership and explicit handoffs. Use with godmode-workflow when runtime, workflow, governance, quality, documentation, or CI concerns need separate analysis.

GodMode Departments

Use this skill only when separate advisory lanes materially clarify a complex task. It does not replace the phases or gates in $godmode-workflow.

Department map

• runtime_platform: environment, toolchain, sandbox, OS, and runtime behavior
• workflow_design: orchestration, prompt, skill, handoff, and state design
• workspace_governance: instructions, release law, branch policy, and scope
• quality_operations: regression strategy, executable gates, and evaluations
• docs_dx: setup guidance, prompts, and user-facing clarity
• ci_security_guardian: CI, CODEOWNERS, dependency automation, and security

Routing contract

• Finish governance preflight before routing departments.
• Delegate proactively only when the user, project guidance, or active skill authorizes it. Keep one delegation depth.
• Give every department an objective, inputs, required output, read-only or explicitly isolated write scope, done criterion, and escalation condition.
• Parallelize only independent lanes. Freeze interface ownership and resolve conflicting advice before implementation.
• Keep department agents advisory by default. Assign tracked implementation to one builder; assign final documentation to scribe only after quality gates.
• Stop department mode once the parent has enough evidence to freeze one plan.

Do not create departments for small tasks or use them as ceremonial reviewers.