Departments

Community

cubetribe

departments

Expanded department-based orchestration for large cross-domain CC_GodMode work. Freezes ownership, handoffs, and write scopes before implementation.

Overview

Publisher	cubetribe
Repository	`ClaudeCode_GodMode-On`
Skill name	`departments`
Stars	54
Forks	10
Bundled files	Instructions only
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by cubetribe on GitHub. Read the source before you install it.

Installation

Install the Departments AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/cubetribe/ClaudeCode_GodMode-On/tree/main/skills/departments
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/cubetribe/ClaudeCode_GodMode-On.git /tmp/ClaudeCode_GodMode-On
mkdir -p .claude/skills
cp -r /tmp/ClaudeCode_GodMode-On/skills/departments .claude/skills/departments

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Departments in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Departments on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Departments is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Departments Mode

Use this skill when one linear workflow is too small for the task because the work crosses multiple ownership areas. Departments Mode is the expanded planning and coordination lane.

It does not replace the existing agents. It groups the existing agents and project surfaces into departments, freezes write scopes, and then routes work through the normal quality gates.

When To Use

runtime, hooks, skills, agents, docs, and release policy change together
a task needs multiple independent research or validation tracks
write ownership is unclear and must be frozen before @builder starts
the work touches plugin packaging plus project templates
the cost of one missed handoff is higher than the coordination overhead

Department Map

Department	Owns	Usual agent support
Runtime Platform	`config/`, hooks, MCP setup, install/runtime behavior	@architect, @builder
Workflow Design	`CLAUDE.md`, `skills/`, `docs/orchestrator/`, orchestration loops	@researcher, @architect
Workspace Governance	`VERSION`, `CHANGELOG.md`, `DECISIONS.md`, policies, templates	@architect, @scribe
Quality Operations	validation scripts, report templates, gate behavior	@tester, @security
Docs & Developer Experience	`README.md`, prompts, onboarding docs, examples	@scribe
CI & GitHub	PR/release framing, CI/CD, GitHub workflow surfaces	@github-manager
API & Contracts	API/type/schema/CLI/public contract surfaces	@api-guardian

Required Artifacts

Create or update these before implementation begins:

intake brief: objective, non-goals, target version, expected validations
department routing map: involved departments and dependency order
write-scope matrix: which files each department owns or must not touch
handoff checklist: what each department must report back

Reports should live under reports/vX.Y.Z/sprint-NN/ and stay concise.

Routing Rules

Run the normal governance and plan-first preflight (sprint file + write scopes, ADR-004).
Use @researcher only for unknown or version-sensitive facts.
Use @architect to freeze the department routing map and write-scope matrix.
Use @api-guardian whenever contracts, schemas, CLI, config, or public behavior change.
Keep @builder as the single implementation writer unless a temporary write lease is explicit.
Use the Core Rule 5 gate combination for this sprint (deterministic hook always; @tester if ux_gate: auto; @security on security surfaces; /code-review on risk or doubt) as the quality gate.
Use @scribe only after quality gates pass.
Use @github-manager only for issue, PR, release, or GitHub surfaces.

Agent Teams

Claude Code Agent Teams can inform this mode, but they are not the default. Use Agent Teams only when the user explicitly asks for teammate-style parallel execution and the work can be split into independent tasks with clear dependencies. Otherwise, use normal Task-tool subagents and concise handoffs.

Stop Conditions

Stop and ask the user before:

changing branch strategy
lowering model quality for critical paths
touching production credentials or live services
pushing, tagging, publishing, or deploying
merging unrelated histories or importing a whole external repository

CC_GodMode — © 2025–2026 Dennis Westermann (dennis-westermann.de). Proprietary — not open source. Free for private, non-commercial use; redistribution or re-hosting outside GitHub is prohibited; attribution required. Official source: github.com/cubetribe/ClaudeCode_GodMode-On. See LICENSE.

Frequently asked questions

What does the Departments AI skill do?

Expanded department-based orchestration for large cross-domain CC_GodMode work. Freezes ownership, handoffs, and write scopes before implementation.

Why use Departments on TypingMind?

Because you install it once and use it with any model. Departments is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Departments in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/cubetribe/ClaudeCode_GodMode-On/tree/main/skills/departments. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Departments?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Departments?

As many as you like. As long as a model supports skills, you can use Departments with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Departments AI skill free?

It is published on GitHub by cubetribe. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Documentation Lookup

affaan-m

CommunityPopular

Use up-to-date library and framework docs via Context7 MCP instead of training data. Activates for setup questions, API references, code examples, or when the user names a framework (e.g. React,…

Everything Claude Code

affaan-m

CommunityPopular

Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.

Discord User Post

Post an approved message as the logged-in Discord user through the Discord desktop app. Use for release announcements or other direct user-authored Discord posts; not for OpenClaw channel sends, bots,…

Test Audit

Invoke whenever writing, changing, reviewing, or sweeping tests. Authoring gate for new tests plus audit workflow for low-value, implementation-coupled, or duplicative tests and the test-only…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Departments Mode

When To Use

Department Map

Required Artifacts

Routing Rules

Agent Teams

Stop Conditions

Frequently asked questions

Related AI Skills

Set up your own AI workspace now