Full-Gates Workflow Definitions
SkillAI & modelsCC_GodMode Full-Gates workflow definitions — used for high-risk work and when Smart Routing escalates. Default routing is Smart Routing (skills/cost-efficiency/).
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Full-Gates Workflow Definitions skill
What this skill tells your AI
The instructions your AI receives, as published by cubetribe/claudecode_godmode-on in skills/workflows/SKILL.md and read by ahel’s review.
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 → @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
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. @validator ∥ @tester (PARALLEL — both MUST pass)
→ 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. @validator ∥ @tester (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. @validator ∥ @tester (PARALLEL)
↓
6. @scribe (document breaking changes)
Critical API Paths
These file patterns always trigger @api-guardian:
src/api/**backend/routes/**shared/types/***.d.tsopenapi.yaml/schema.graphql**/interfaces/**
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" → @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
Signals
- GitHub stars
- 51
- Forks
- 8
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
workflows-cubetribe- Source
- github.com/cubetribe/claudecode_godmode-on