cubetribe

Ultracode / Max-Parallel mode — dynamic workflows fan work out across tens–hundreds of adversarially-verified parallel subagents for large, decomposable jobs (codebase-wide audits, big migrations, cross-checked research). Opt-in; higher token spend.

Smart Routing — the DEFAULT CC_GodMode routing policy. Risk-based, minimal-agent paths that preserve required safety gates for the changed scope.

Release sprint workflow: version-at-release via tooling, CHANGELOG [Unreleased] flow, release invariant checks, tags, GitHub Releases, RCs. Authoritative law: docs/orchestrator/VERSIONING.md

Plan-first orchestration (ADR-004): comprehensive PLAN.md, sprint files with write-scope ownership, preflight checks, serialized integration, and the release sprint. Use for any non-trivial or multi-part request BEFORE dispatching agents.

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

Bootstrap repo-local governance before CC_GodMode workflows run in an empty, newly initialized, or undocumented workspace. Use proactively when a project has no CLAUDE.md, no README, or no clear structure yet.

Meta-decision logic that adapts workflows based on task analysis — security overrides, breaking change escalation, performance paths, emergency hotfix, and documentation optimization

Parallel quality gate orchestration — @validator and @tester run simultaneously after @builder, with mandatory decision matrix for pass/fail routing

Create controlled, local-first document case files with immutable intake, native PDF extraction, page-scoped OCR escalation, evidence anchors, validation gates, and reproducible archives. Use when Codex must organize or verify sensitive tax, legal, compliance, audit, or administrative paperwork without silently installing tools, uploading documents, submitting forms, deleting originals, or treating model output as verified evidence.

Reproduce, isolate, fix, and re-test regressions or runtime failures with bounded evidence gathering, one implementation writer, and outcome-based verification. Use with godmode-workflow when a failure needs diagnosis before repair.

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.

Build a disposable local-only prototype through a fast single-writer loop with mandatory watermarks and end-to-end outcome evidence. Use only when production correctness, security review, and release readiness are explicitly deferred.

Perform a findings-first code, architecture, contract, or release-risk review with bounded read-only specialists and evidence-backed severity. Use when the requested outcome is assessment rather than implementation.

Orchestrate non-trivial Codex delivery through governance and capability preflight, bounded parallel discovery, a frozen single-writer contract, independent validation, outcome evidence, and release handoff. Use for complex implementation, migration, or release work that benefits from coordinated subagents.

Apply conservative best practices for SwiftUI work on macOS and iOS, including state flow, target-safe changes, and focused Xcode validation.

Apply conservative best practices for Flutter and Dart work, including composable widgets, explicit state boundaries, and focused analyze/test runs.

Strategically reviews code changes, diffs, and agent reports from Claude Code GodMode or Codex sessions. Writes advisory findings to .cowork/code-reviews/ only when review output is requested, and never creates implementation tasks or authorizes executor work. Use when the user asks to review the last GodMode run, check executor output, validate a release, or audit recent commits.

Creates structured HANDOFF.md briefs for Cowork-to-executor handoff. Includes mission, context files, acceptance criteria, constraints, approval status, write scope, and CC_GodMode Restart-Prompt. Use only when the user explicitly asks to create or update a handoff document, says 'übergib an GodMode', 'erstelle HANDOFF.md', or 'mach ne Übergabe'.

Drafts the next structured prompt for Claude Code or OpenAI Codex executor sessions. Produces mission, context files, acceptance criteria, constraints, and approval placeholders, but does not authorize implementation. Use when the user explicitly asks to prepare or update .cowork/pending-prompt.md, asks 'what's the next prompt', 'prep this for GodMode', or 'bereite den nächsten Prompt vor'.

Acts as guardian for local coding projects integrated with the Cowork Singularität. Monitors project state, reads .cowork/status.json and recent reports, flags open handoffs, stale sessions, version drift, and policy violations. Use when the user asks about project status, what's pending, where we left off, what GodMode did last, session continuity, says 'status check', 'wie ist der Stand', 'was läuft', or 'health check'.

Performs an on-demand external audit of a running or recently-completed GodMode session to detect scope-creep, drift from original mission, and context pollution. Compares the original mission brief against actual file changes and recent agent reports. The PRIMARY skill of Cowork Singularität — Dennis uses this as gut-check when he suspects autonomous GodMode is running off-track. Use when user says 'sanity check', 'audit GodMode', 'läuft das noch richtig', 'spinnt der', 'prüf den Stand', 'is GodMode on track', 'check for drift', or 'scope creep check'.

Restores Cowork session context for Singularität coding projects after a fresh start or /compact. Reads .cowork/status.json, recent handoff-log entries, project memory, and last reports to brief Cowork on where to pick up. Use at session start when working on an existing Singularität project, after compaction, or when the user says 'continue', 'resume', 'where were we', 'mach weiter', 'zurück zum Projekt'.

Self-orchestrating multi-agent development workflows. You say WHAT, the AI decides HOW.

Default GitHub governance skill for repository work, pull requests, branch safety, merges, releases, versioning, CODEOWNERS, protected branches, rulesets, CI checks, and collaboration conflict prevention. Use whenever the user mentions GitHub, git, branches, pull requests, merges, release impact, changelog, version bumps, CODEOWNERS, branch protection, rulesets, or version conflicts.