Ccg

How It Works

1. Claude decomposes the request into two advisor prompts:
   - Codex prompt (analysis/architecture/backend)
   - Gemini prompt (UX/design/docs/alternatives)

2. Claude runs via CLI (skill nesting not supported):
   - `omc ask codex "<codex prompt>"`
   - `omc ask gemini "<gemini prompt>"`

3. Artifacts are written under `.omc/artifacts/ask/`

4. Claude synthesizes both outputs into one final response

Execution Protocol

When invoked, Claude MUST follow this workflow:

1. Decompose Request

Split the user request into:

• Codex prompt: architecture, correctness, backend, risks, test strategy
• Gemini prompt: UX/content clarity, alternatives, edge-case usability, docs polish
• Synthesis plan: how to reconcile conflicts

2. Invoke advisors via CLI

Note: Skill nesting (invoking a skill from within an active skill) is not supported in Claude Code. Always use the direct CLI path via Bash tool.

Run both advisors:

omc ask codex "<codex prompt>"
omc ask gemini "<gemini prompt>"

3. Collect artifacts

Read latest ask artifacts from:

.omc/artifacts/ask/codex-*.md
.omc/artifacts/ask/gemini-*.md

4. Synthesize

Return one unified answer with:

• Agreed recommendations
• Conflicting recommendations (explicitly called out)
• Chosen final direction + rationale
• Action checklist

Fallbacks

If one provider is unavailable:

• Continue with available provider + Claude synthesis
• Clearly note missing perspective and risk

If both unavailable:

• Fall back to Claude-only answer and state CCG external advisors were unavailable

Invocation

/oh-my-claudecode:ccg <task description>

Example:

/oh-my-claudecode:ccg Review this PR - architecture/security via Codex and UX/readability via Gemini