Skill v1.0.1
currentAutomated scan100/100+4 new
version: "1.0.1" name: workflows description: "CC_GodMode Full-Gates workflow definitions — used for high-risk work and when Smart Routing escalates. Default routing is Smart Routing (skills/cost-efficiency/)." license: "Proprietary - (c) 2025-2026 Dennis Westermann. Free for private non-commercial use; redistribution/re-hosting prohibited. See LICENSE: github.com/cubetribe/ClaudeCode_GodMode-On"
Full-Gates Workflow Definitions
These are the Full-Gates workflows, used for high-risk work and when Smart Routing escalates. Default routing is Smart Routing (skills/cost-efficiency/).
Architecture gate split: For small/medium tasks (no new modules, no breaking changes) the Orchestrator writes a 3–5 bullet inline architecture brief into reports/vX.Y.Z/sprint-NN/01-architect-report.md without invoking @architect. For new modules, breaking changes, cross-domain designs, or uncertain scope, invoke @architect (Opus) via Task tool.
Use docs/orchestrator/MODES.md and the relevant mode skill when the request is a prototype, cross-domain department run, or explicit Agent Teams run.
Workflow Selection
| Command Pattern | Workflow | Agents | |
|---|---|---|---|
| "New Feature: [X]" | Feature | (@researcher) → @architect → @builder → checks → @scribe | |
| "Bug Fix: [X]" | Bug Fix | @builder → checks | |
| "API Change: [X]" | API Change | (@researcher) → @architect → @api-guardian → @builder → checks → @scribe | |
| "Refactor: [X]" | Refactor | @architect → @builder → checks | |
| "Research: [X]" | Research | @researcher → report | |
| "Process Issue #X" | Issue | @github-manager loads → analyze → select workflow → PR | |
| "Prepare Release" | Release | @scribe → @github-manager |
(@researcher) = optional, use when new tech/libraries need evaluation
Feature Workflow (Full)
User Request → "New Feature: [X]"↓1. @researcher (OPTIONAL — if new tech involved)→ Report: technology evaluation, best practices, risks↓2. @architect→ Architecture Decision Record (ADR)→ Module structure, interfaces, tech choices↓3. @builder→ Implementation following @architect specs→ All code changes, tests, types↓4. checks (Core Rule 5 — deterministic hook always; @tester, @security, /code-review as declared/applicable, PARALLEL)→ See quality-gates skill for decision matrix↓5. @scribe→ VERSION bump, CHANGELOG, documentation
Bug Fix Workflow (Minimal)
User Request → "Bug Fix: [X]"↓1. @builder (fix implementation)↓2. checks (Core Rule 5 — deterministic hook always; @tester, @security, /code-review as declared/applicable, PARALLEL)↓3. INTEGRATE — @scribe adds the `[Unreleased]` CHANGELOG entry (Core Rule 11: every sprint, even one-line fixes)
API Change Workflow (Strict)
MANDATORY @api-guardian — never skip for API changes.
User Request → "API Change: [X]"↓1. @researcher (OPTIONAL)↓2. @architect (API design, contract definition)↓3. @api-guardian (MANDATORY)→ Consumer impact analysis→ Breaking change detection→ Migration strategy↓4. @builder (implementation + consumer updates)↓5. checks (Core Rule 5 — deterministic hook always; @tester, @security, /code-review as declared/applicable, PARALLEL)↓6. @scribe (document breaking changes)
Critical API Paths
API/schema/type paths always trigger @api-guardian. The canonical path list lives in skills/api-change/ and nowhere else — this file does not repeat it.
Research Workflow (Standalone)
User Request → "Research: [X]"↓1. @researcher→ Web research, documentation lookup→ Technology evaluation matrix→ Report with sources and recommendations↓2. Report saved to reports/vX.Y.Z/sprint-NN/00-researcher-report.md
Issue Processing Workflow
User Request → "Process Issue #X"↓1. @github-manager loads issue from GitHub↓2. Orchestrator analyzes:→ Type: Bug / Feature / Enhancement→ Complexity: Low / Medium / High→ Areas: API / UI / Backend / Infrastructure↓3. Select appropriate workflow (Feature/Bug/API)↓4. Execute workflow↓5. @github-manager creates PR with "Fixes #X"
Release Workflow
User Request → "Prepare Release"↓1. @scribe→ Verify VERSION is incremented→ Verify CHANGELOG is updated→ Verify all reports are in place↓2. @github-manager→ Create release PR→ Tag version→ Create GitHub Release
Agent Invocation
All agents are called via the Task tool with subagent_type:
Task tool → subagent_type: "architect" → @architectTask tool → subagent_type: "api-guardian" → @api-guardianTask tool → subagent_type: "builder" → @builderTask tool → subagent_type: "tester" → @testerTask tool → subagent_type: "security" → @securityTask tool → subagent_type: "scribe" → @scribeTask tool → subagent_type: "github-manager" → @github-managerTask tool → subagent_type: "researcher" → @researcher
CC_GodMode — © 2025–2026 Dennis Westermann ([dennis-westermann.de](https://www.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](https://github.com/cubetribe/ClaudeCode_GodMode-On). See LICENSE.