From cc-godmode
Defines workflows that orchestrate agents for tasks like features, bug fixes, API changes, refactors, research, GitHub issues, and releases. Auto-selects via command patterns like 'New Feature: [X]' in CC_GodMode.
npx claudepluginhub cubetribe/claudecode_godmode-onThis skill uses the workspace's default tool permissions.
The Orchestrator selects workflows automatically based on task type.
Guides Cursor (PM) ↔ Claude Code (Worker) two-agent workflow using Plans.md markers for task assignment, implementation, review, CI fixes, and deployment.
Orchestrates epic-to-PR workflows via 4-phase execution (pre-flight, working, validation, submit) and 6-tier agent hierarchy for multi-agent teams on issues/tasks.
Orchestrates subagents by delegating tasks to role-matched specialists like engineer, reviewer, analyst for multi-agent coding workflows.
Share bugs, ideas, or general feedback.
The Orchestrator selects workflows automatically based on task type.
| Command Pattern | Workflow | Agents |
|---|---|---|
| "New Feature: [X]" | Feature | (@researcher) → @architect → @builder → @validator ∥ @tester → @scribe |
| "Bug Fix: [X]" | Bug Fix | @builder → @validator ∥ @tester |
| "API Change: [X]" | API Change | (@researcher) → @architect → @api-guardian → @builder → @validator ∥ @tester → @scribe |
| "Refactor: [X]" | Refactor | @architect → @builder → @validator ∥ @tester |
| "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
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. @validator ∥ @tester (PARALLEL — both MUST pass)
→ See quality-gates skill for decision matrix
↓
5. @scribe
→ VERSION bump, CHANGELOG, documentation
User Request → "Bug Fix: [X]"
↓
1. @builder (fix implementation)
↓
2. @validator ∥ @tester (PARALLEL)
↓
3. COMPLETE (no @scribe for patches unless significant)
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. @validator ∥ @tester (PARALLEL)
↓
6. @scribe (document breaking changes)
These file patterns always trigger @api-guardian:
src/api/**backend/routes/**shared/types/***.d.tsopenapi.yaml / schema.graphql**/interfaces/**User Request → "Research: [X]"
↓
1. @researcher
→ Web research, documentation lookup
→ Technology evaluation matrix
→ Report with sources and recommendations
↓
2. Report saved to reports/vX.X.X/00-researcher-report.md
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"
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
All agents are called via the Task tool with subagent_type:
Task tool → subagent_type: "architect" → @architect
Task tool → subagent_type: "api-guardian" → @api-guardian
Task tool → subagent_type: "builder" → @builder
Task tool → subagent_type: "validator" → @validator
Task tool → subagent_type: "tester" → @tester
Task tool → subagent_type: "scribe" → @scribe
Task tool → subagent_type: "github-manager" → @github-manager
Task tool → subagent_type: "researcher" → @researcher