菜单
Meta-decision logic that adapts workflows based on task analysis — security overrides, breaking change escalation, performance paths, emergency hotfix, and documentation optimization
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
| name | meta-decisions |
| description | Meta-decision logic that adapts workflows based on task analysis — security overrides, breaking change escalation, performance paths, emergency hotfix, and documentation optimization |
The meta-decision layer analyzes user prompts and automatically adapts workflows.
| Rule | Trigger Keywords | Workflow Adaptation |
|---|---|---|
| securityOverride | auth, jwt, token, password, encrypt, session | Force @validator security-focused check |
| breakingChangeEscalation | breaking change, deprecate, remove API, migration | Require @architect review before any change |
| performanceCriticalPath | performance, optimize, slow, latency, cache | Add performance benchmarks to @tester |
| emergencyHotfix | hotfix, urgent, critical, production down | Streamlined workflow: @builder → @validator only |
| documentationOnly | docs only, readme, typo fix | Skip @builder, direct to @scribe. Precedence: if the change WRITES release artifacts (VERSION, CHANGELOG.md beyond the sprint-integration [Unreleased] entry), the release-artifact risk signal wins and the release law applies (docs/orchestrator/VERSIONING.md) |
User Prompt Received
↓
analyze-prompt.js evaluates:
↓
┌─ Security keywords? → securityOverride
├─ Breaking change? → breakingChangeEscalation
├─ Performance? → performanceCriticalPath
├─ Emergency? → emergencyHotfix
└─ Docs only? → documentationOnly
↓
None matched → Standard workflow selection
Significant decisions are logged in DECISIONS.md:
## ADR-[NUMBER]: [Title]
**Date:** YYYY-MM-DD
**Status:** Accepted / Superseded / Deprecated
**Context:** [Why this decision was needed]
**Decision:** [What was decided]
**Consequences:** [Impact of the decision]
For complex decisions, use the RARE matrix:
| Role | Agent | Responsibility |
|---|---|---|
| Responsible | @builder | Does the work |
| Accountable | Orchestrator | Ensures completion |
| Reviewed by | @validator + @tester | Quality assurance |
| Escalated to | User | Final authority |
When the Orchestrator cannot decide:
When processing issues, the meta-layer adds:
{
"type": "feature|bug|enhancement",
"complexity": "low|medium|high",
"areas": ["api", "ui", "backend"],
"meta_rules_triggered": ["securityOverride"],
"workflow_adaptation": "Added security-focused @validator check"
}
When emergencyHotfix is triggered:
User: "Hotfix: production login broken"
↓
@builder (immediate fix)
↓
@validator (security + unit tests only)
↓
DONE (skip @tester, @scribe — speed over process)
Post-hotfix: Schedule a follow-up with full quality gates.