oh-my-customcode 0.158.0 → 0.159.0

package/templates/.claude/skills/agora/SKILL.md

@@ -1,288 +0,0 @@
----
-name: omcustom:agora
-description: "Multi-LLM adversarial consensus loop — 3+ LLMs compete to find flaws in designs/specs until unanimous agreement is reached"
-user-invocable: true
-argument-hint: "<document-path> [--rounds N] [--severity-threshold HIGH]"
-effort: max
-scope: core
-version: 1.0.0
-source:
-  type: external
-  origin: github
-  url: https://github.com/baekenough/baekenough-skills
-  version: 1.0.0
----
-
-# Agora: Multi-LLM Adversarial Consensus
-
-3개 이상의 LLM(Claude, Codex/GPT, Gemini)이 경쟁적으로 설계/문서의 결함을 찾고, 만장일치 합의에 도달할 때까지 반복하는 적대적 교차 검증 스킬.
-
-## Prerequisites
-
-- `codex-exec` skill (Codex/GPT 호출)
-- `gemini-exec` skill (Gemini 호출)
-- Agent Teams enabled (`CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1`) or Agent tool available
-
-## Usage
-
-```
-/agora docs/design.md                          # Default: 3 LLMs, unlimited rounds
-/agora docs/design.md --rounds 10              # Max 10 rounds
-/agora docs/design.md --severity-threshold HIGH # Exit when no HIGH+ findings
-/agora docs/design.md --models claude,codex     # 2 LLMs only
-```
-
-## Workflow
-
-### Phase 1: Setup
-1. Read the target document
-2. Create Agent Team: `TeamCreate("agora-review")`
-3. Create review tasks per focus area
-
-### Phase 2: Spawn Reviewers (parallel)
-Spawn 3 reviewers as Agent Team members:
-
-```
-Agent(name: "claude-critic", model: opus, effort: max)
-  → 20-point deep adversarial review
-  
-Agent(name: "codex-critic", model: opus)
-  → Invoke Skill(codex-exec) for GPT perspective + independent Claude analysis
-  
-Agent(name: "gemini-critic", model: opus)  
-  → Invoke Skill(gemini-exec) for Gemini perspective + independent Claude analysis
-```
-
-### Phase 3: Independent Review
-Each reviewer performs adversarial review with this template:
-
-```
-For EACH review point:
-### Round N: [Topic]
-**Severity**: CRITICAL / HIGH / MEDIUM / LOW
-**Flaw**: [Specific, concrete problem description]
-**Evidence**: [Why this is real, not theoretical]
-**Impact**: [What happens if not addressed]
-**Counter-argument**: [Best case FOR the current design]
-**Verdict**: KEEP / MODIFY / REJECT
-```
-
-Review areas (adapt to document type):
-- Architecture fundamentals
-- Component/service design
-- Data architecture
-- Security & resilience
-- Feasibility & deployment
-- Testing strategy
-- Operational complexity
-
-### Phase 4: Cross-Review (Peer-to-Peer)
-Each reviewer sends findings to the other two via `SendMessage`.
-
-Counter-review template:
-1. Which findings do you **AGREE** with? (and why)
-2. Which findings do you **DISAGREE** with? (evidence-based rebuttal)
-3. What did they **MISS** that you caught?
-4. What did they catch that you **MISSED**?
-5. **SEVERITY** adjustments — upgrade or downgrade with justification
-
-### Phase 5: Synthesis
-Team lead aggregates all findings:
-
-```
-UNANIMOUS CRITICAL: [findings all 3 agreed on]
-STRONG AGREEMENT:   [findings 2/3 agreed on]
-SPLIT DECISIONS:    [findings with disagreement + resolution]
-```
-
-Determine verdict:
-- **BUILD**: No CRITICAL, no unresolved HIGH
-- **BUILD WITH CHANGES**: No CRITICAL, HIGH findings have accepted mitigations
-- **REDESIGN**: Any unresolved CRITICAL findings
-- **ABANDON**: Fundamental concept is flawed
-
-### Phase 6: Loop (if REDESIGN)
-1. Team lead produces/delegates redesign addressing ALL critical findings
-2. New version sent to ALL reviewers: `SendMessage(to: "*")`
-3. Reviewers re-review → GOTO Phase 4
-4. Repeat until EXIT criteria met
-
-### Phase 7: Exit (consensus reached)
-When ALL reviewers agree BUILD or BUILD WITH CHANGES:
-1. Produce final consensus report
-2. Write to `.claude/outputs/sessions/{date}/agora-{topic}-{time}.md`
-
-### Tool: Writing artifacts under .claude/outputs/
-
-Direct Write to `.claude/outputs/sessions/{date}/agora-{topic}-{time}.md` is permitted under `mode: "bypassPermissions"` (CC v2.1.121+, #1101). Write tool auto-creates parent directory. For CC < v2.1.121, see git history for the legacy /tmp bypass pattern.
-
-3. Shut down team: `SendMessage(to: "*", message: {type: "shutdown_request"})`
-
-## Reviewer Principles
-
-1. **NEUTRAL** — no reviewer has home team advantage
-2. **COMPETITIVE** — find flaws others missed
-3. **CRITICAL** — "fewer than 5 CRITICAL flaws = not looking hard enough"
-4. **EVIDENCE-BASED** — every finding cites specific evidence
-5. **CONSTRUCTIVE** — every flaw includes recommended fix
-6. **CONVERGENT** — goal is consensus, not endless disagreement
-
-## Consensus Criteria
-
-| Condition | Required |
-|-----------|----------|
-| CRITICAL findings resolved | ALL |
-| HIGH findings resolved or accepted | ALL |
-| All reviewers rate BUILD or BUILD WITH CHANGES | YES |
-| Cross-review disagreements resolved | ALL |
-
-## Output Format
-
-```markdown
-# Agora Consensus Report
-
-## Document: [path]
-## Rounds: [N]
-## Reviewers: [list with LLM models used]
-
-## Verdict: [BUILD / BUILD WITH CHANGES / REDESIGN]
-
-## Unanimous Findings
-| # | Finding | Severity | All 3 Agree |
-|---|---------|----------|-------------|
-
-## Required Changes Before Build
-1. [change with source reviewer]
-2. ...
-
-## Accepted Risks
-- [finding accepted with justification]
-
-## Unique Contributions Per Reviewer
-| Reviewer | Findings Others Missed |
-|----------|----------------------|
-
-## Process Metrics
-- Rounds: N
-- Total findings: N
-- Cross-adopted: N
-- Severity upgrades: N
-- Severity downgrades: N
-- Disagreements raised: N
-- Disagreements resolved: N/N
-```
-
-## Configuration
-
-```yaml
-# Default settings
-agora:
-  max_rounds: unlimited       # Set --rounds to limit
-  severity_threshold: HIGH    # EXIT when no findings >= threshold
-  models:
-    - claude (opus, max effort)
-    - codex (via codex-exec skill)
-    - gemini (via gemini-exec skill)
-  review_points: 20           # Per reviewer
-  cross_review: true          # Peer-to-peer sharing
-  auto_redesign: true         # Auto-produce redesign on REDESIGN verdict
-```
-
-## Anti-Patterns
-
-| Anti-Pattern | Why Wrong | Correct |
-|-------------|-----------|---------|
-| Single LLM review | Misses blind spots | 3+ LLMs find complementary flaws |
-| No cross-review | Reviewers don't challenge each other | Peer-to-peer sharing surfaces disagreements |
-| Accepting first BUILD | May miss edge cases | Loop until ALL agree |
-| Ignoring split decisions | Unresolved disagreements fester | Resolve every split with evidence |
-| Push for consensus too fast | Premature agreement | Let reviewers challenge freely |
-
-When spawning agents via the Agent tool during this skill's execution, always pass `mode: "bypassPermissions"`. The Agent tool default (`acceptEdits`) overrides agent frontmatter `permissionMode`, causing permission prompts during unattended execution.
-
-## Ontology Convergence (PoC)
-
-> Source: #993 (from ouroboros #966 re-evaluation, Option C deferred → PoC 섹션으로 내재화)
-> Status: Experimental — default disabled
-
-agora는 기본적으로 만장일치 기반으로 종료하지만, 의미적 유사도 기반 조기 종료를 **PoC로 지원**합니다.
-
-### Rationale
-
-여러 라운드 후 모든 에이전트의 마지막 응답이 의미상 거의 동일하면(semantic similarity ≥ threshold), 만장일치를 기다리지 않고 조기 수렴으로 판단하여 토큰 비용을 절감합니다.
-
-### Configuration
-
-```yaml
-ontology_convergence:
-  enabled: false              # 기본 비활성 (PoC)
-  threshold: 0.95             # cosine similarity 최소값
-  min_rounds: 2               # 최소 라운드 (너무 이른 종료 방지)
-  embedding_model: voyage-3.5 # 또는 openai-text-embedding-3
-```
-
-### Algorithm
-
-1. 각 라운드 종료 시 participant 응답의 embedding 계산
-2. Pairwise cosine similarity 매트릭스 생성
-3. 최소 유사도(min pairwise similarity) 계산
-4. `min_sim ≥ threshold` AND `rounds ≥ min_rounds` → 조기 종료
-
-### Trade-offs
-
-| 장점 | 단점 |
-|------|------|
-| 토큰 절감 (수렴 시 2-3 라운드 단축) | embedding 계산 오버헤드 |
-| 만장일치 편향 완화 (의미 일치만으로 충분) | threshold 튜닝 필요 (프로젝트마다 다름) |
-| 정량적 수렴 지표 | 오분류 시 조기 종료 리스크 |
-
-### Activation
-
-현재 PoC 단계. 활성화 시 `agora` 스킬 호출 파라미터에 `--ontology-convergence=true` 추가. 프로덕션 승격 결정은 3개월 후 데이터 기반 재평가 (연계: #992 PAL Router Defer+observe 전략과 동일 원칙).
-
-### Cross-references
-
-- #993 (source)
-- #966 ouroboros 재평가
-- guides/agent-design/pal-cost-routing-analysis.md (유사한 Defer+observe 전략)
-
-## Anti-Groupthink Mode (Optional)
-
-`agora`의 기본 워크플로우는 만장일치 수렴(convergence)이 목표지만, 토론 과정에서 집단사고(Groupthink) 위험이 있을 때 anti-groupthink mode를 활성화할 수 있습니다.
-
-### Activation
-
-스킬 호출 시 인자로 활성화:
-```
-/agora docs/design.md --mode anti-groupthink
-```
-
-### Mechanisms
-
-| 메커니즘 | 동작 |
-|---------|------|
-| Devil's Advocate slot | 리뷰어 1명이 전담 반대자 역할 — 합의 형성 시도에 항상 반대 입장 견지 |
-| Minority opinion protection | 1명만 주장하는 의견도 보존, 기각 시 명시적 정당화(3개 근거) 필수 |
-| Round soft cap | 라운드 3회 도달 시 합의 미도달 영역은 "합의 없음 — 분기 결정 필요"로 종결 (기본 워크플로우는 무한 루프 가능) |
-
-### Reviewer Role Adjustment
-
-기본 모드(3 reviewers)에 anti-groupthink mode 적용 시:
-- `claude-critic` → Devil's Advocate 전담 (모든 합의 시도에 반대 입장)
-- `codex-critic`, `gemini-critic` → 일반 리뷰 (변경 없음)
-
-Round soft cap이 작동하면 최종 보고서에 "UNRESOLVED — BRANCHING DECISION NEEDED" 섹션이 추가됩니다.
-
-### When to Use Anti-Groupthink Mode vs roundtable-debate
-
-| 상황 | 권장 스킬 |
-|------|---------|
-| 합의가 *필요*하지만 위험 발굴도 필요 | `agora --mode anti-groupthink` |
-| 합의 자체가 *불필요*, 다양한 시각이 산출물 | `roundtable-debate` |
-| 단순 검증 (통과/실패) | `agora` (기본 모드) |
-
-자세한 비교는 `guides/multi-agent-debate-patterns/` 가이드 참조 (별도 wave에서 생성 예정).
-
-### Attribution
-
-Devil's Advocate + minority protection 메커니즘은 cc-roundtable 패턴에서 차용되었습니다. (`roundtable-debate` 스킬과 공유 메커니즘)

package/templates/.claude/skills/codex-exec/SKILL.md

@@ -1,259 +0,0 @@
----
-name: codex-exec
-description: Execute OpenAI Codex CLI prompts and return results
-scope: core
-argument-hint: "<prompt> [--json] [--output <path>] [--model <name>] [--timeout <ms>] [--effort <level>]"
-user-invocable: true
----
-
-# Codex Exec Skill
-
-Execute OpenAI Codex CLI prompts in non-interactive mode and return structured results. Enables Claude + Codex hybrid workflows.
-
-## Options
-
-```
-<prompt>          Required. The prompt to send to Codex CLI
---json            Return structured JSON Lines output
---output <path>   Save final message to file
---model <name>    Model override (default: Codex CLI default model)
---timeout <ms>    Execution timeout (default: 120000, max: 600000)
---full-auto       Enable auto-approval mode (codex -a full-auto)
---working-dir     Working directory for Codex execution
---effort <level>  Set reasoning effort level (minimal, low, medium, high, xhigh)
-                  Maps to Codex CLI's model_reasoning_effort config
-                  Default: uses Codex CLI's configured default
-                  Recommended: xhigh for research/analysis tasks
-```
-
-## Workflow
-
-```
-1. Pre-checks
-   - Verify `codex` binary is installed (which codex || npx codex --version)
-   - Verify authentication (OPENAI_API_KEY or logged in)
-2. Build command
-   - Base: codex exec --ephemeral "<prompt>"
-   - Apply options: --json, --model, --full-auto, -C <dir>
-   - Set --working-dir if specified
-3. Execute
-   - Run via Bash tool with timeout (default 2min, max 10min)
-   - Or use helper script: node .claude/skills/codex-exec/scripts/codex-wrapper.cjs
-4. Parse output
-   - Text mode: return raw stdout
-   - JSON mode: parse JSON Lines, extract final assistant message
-5. Report results
-   - Format output with execution metadata
-```
-
-## Safety Defaults
-
-- `--ephemeral`: No session persistence (conversations not saved)
-- Default mode: Normal approval (Codex prompts for confirmation)
-- Override with `--full-auto` only when explicitly requested
-
-## Output Format
-
-### Success (Text Mode)
-```
-[Codex Exec] Completed
-
-Model: (default)
-Duration: 23.4s
-Working Dir: /path/to/project
-
---- Output ---
-{codex response text}
-```
-
-### Success (JSON Mode)
-```
-[Codex Exec] Completed (JSON)
-
-Model: (default)
-Duration: 23.4s
-Events: 12
-
---- Final Message ---
-{extracted final assistant message}
-```
-
-### Failure
-```
-[Codex Exec] Failed
-
-Error: {error_message}
-Exit Code: {code}
-Suggested Fix: {suggestion}
-```
-
-## Helper Script
-
-For complex executions, use the wrapper script:
-```bash
-node .claude/skills/codex-exec/scripts/codex-wrapper.cjs --prompt "your prompt" [options]
-```
-
-The wrapper provides:
-- Environment validation (binary + auth checks)
-- Safe command construction
-- JSON Lines parsing with event extraction
-- Structured JSON output
-- Timeout handling with graceful termination
-
-## Examples
-
-```bash
-# Simple text prompt
-codex-exec "explain what this project does"
-
-# JSON output with model override
-codex-exec "list all TODO items" --json
-
-# Save output to file
-codex-exec "generate a README" --output ./README.md
-
-# Full auto mode with custom timeout
-codex-exec "fix the failing tests" --full-auto --timeout 300000
-
-# Specify working directory
-codex-exec "analyze the codebase" --working-dir /path/to/project
-```
-
-## Integration
-
-Works with the orchestrator pattern:
-- Main conversation delegates Codex execution via this skill
-- Results are returned to the main conversation for further processing
-- Can be chained with other skills (e.g., dev-review after Codex generates code)
-
-## Availability Check
-
-codex-exec requires the Codex CLI binary to be installed and authenticated. The skill is only usable when:
-
-1. `codex` binary is found in PATH (`which codex` succeeds)
-2. Authentication is valid (OPENAI_API_KEY set or `codex` logged in)
-
-If either check fails, this skill cannot be used. Fall back to Claude agents for the task.
-
-> **Note**: This skill is invoked via `/codex-exec` command, delegated by the orchestrator, or suggested by routing skills when codex is available. The intent-detection system can trigger it for research (xhigh) and code generation (hybrid) workflows.
-
-## Agent Teams Integration
-
-When used within Agent Teams (requires explicit invocation):
-
-1. **As delegated task**: orchestrator explicitly delegates codex-exec for code generation
-2. **Hybrid workflow**: Claude team member analyzes → orchestrator invokes codex-exec → Claude reviews
-3. **Iteration**: Team messaging enables review-fix cycles between Claude and Codex outputs
-
-```
-Orchestrator delegates generation task
-  → /codex-exec invoked explicitly
-  → Output returned to orchestrator
-  → Reviewer validates quality
-  → Iterate if needed
-```
-
-## Research Workflow
-
-When the orchestrator or intent-detection detects a research/information gathering request (routing_rule in agent-triggers.yaml):
-
-1. **Check Codex availability**: Verify `codex` binary and `OPENAI_API_KEY`
-2. **If available**: Execute with xhigh reasoning effort for thorough research
-3. **If unavailable**: Fall back to Claude's WebFetch/WebSearch
-
-### Research Command Pattern
-
-```
-/codex-exec "Research and analyze: {topic}. Provide structured findings with sources." --effort xhigh --full-auto --json
-```
-
-### Effort Level Guide
-
-| Level | Use Case | Speed | Depth |
-|-------|----------|-------|-------|
-| minimal | Quick lookups | Fastest | Surface |
-| low | Simple queries | Fast | Basic |
-| medium | General tasks | Balanced | Standard |
-| high | Complex analysis | Slower | Deep |
-| xhigh | Research & investigation | Slowest | Maximum |
-
-## Code Generation Workflow
-
-When routing skills detect a code generation task and codex is available:
-
-1. **Check availability**: Verify codex CLI via `/tmp/.claude-env-status-*`
-2. **If available + new file creation**: Suggest hybrid workflow
-3. **Hybrid pattern**:
-   - codex-exec generates initial code (fast, broad generation)
-   - Claude expert reviews for quality, patterns, best practices
-   - Iterate if needed
-
-### Suitable Tasks
-- New file scaffolding
-- Boilerplate generation
-- Test stub creation
-- Documentation generation
-
-### Unsuitable Tasks
-- Modifying existing code (Claude expert better at understanding context)
-- Architecture decisions (requires reasoning, not generation)
-- Bug fixes (requires deep code understanding)
-
-### Code Generation Command Pattern
-```
-/codex-exec "Generate {description} following {framework} best practices" --effort high --full-auto
-```
-
-## Browser Verify Workflow (Codex + claude-in-chrome 협업 루프)
-
-Codex가 생성/수정한 프론트엔드 결과를 시각적으로 검증하는 루프 패턴. 신규 스킬 불요 — 기존 도구 조합.
-
-### Pattern
-
-```
-codex-exec "build/fix frontend"
-    → bun dev / npm run dev (로컬 서버 기동)
-    → claude-in-chrome:navigate(localhost:port)
-    → claude-in-chrome:gif_creator(action capture)
-    → claude-in-chrome:read_console_messages (오류 감지)
-    → claude-in-chrome:read_network_requests (실패 호출 감지)
-    → 오류 있으면: codex-exec "fix: {error context}" → 루프 재진입
-    → 오류 없으면: 종료 + 결과 보고
-```
-
-### When to Use
-
-| 상황 | 권장 |
-|------|------|
-| 단순 코드 생성 | `codex-exec` 단독 |
-| 프론트엔드 시각 검증 필요 | **이 루프** |
-| API/백엔드 검증 | `deep-verify` skill |
-| 복잡한 디자인 시스템 | `design-shotgun` 병행 |
-
-### Loop Termination Rules
-
-- 최대 반복 3회 (degeneration 방지, R013/agora 패턴 차용)
-- console error 0개 + network failure 0개 → 종료
-- 동일 오류 반복 시 즉시 종료 + 사용자 보고
-
-### Tool Composition
-
-| 단계 | 도구 |
-|------|------|
-| Build/Fix | `codex-exec` |
-| Server | `Bash(bun dev)` (background) |
-| Visual | `mcp__claude-in-chrome__navigate` + `gif_creator` |
-| Diagnose | `read_console_messages` + `read_network_requests` |
-
-자세한 구현 패턴: `guides/browser-automation/01-browser-automation-patterns.md` 참조.
-
-> **Tool**: Use the **Write tool** for any artifact files this loop produces — never Bash mkdir on `.claude/outputs/`.
-
-### Tool: Writing artifacts under .claude/outputs/
-
-Direct Write to `.claude/outputs/codex/sessions/{date}/codex-{HHmmss}.{ext}` is permitted under `mode: "bypassPermissions"` (CC v2.1.121+, #1101). Write tool auto-creates parent directory. For CC < v2.1.121, see git history for the legacy /tmp bypass pattern.
-
-### Attribution
-
-Pattern source: Codex Browser Use (https://x.com/jameszmsun/status/2047522852854026378), scout #1009.