一键导入
orch-panel
Invoke a Panel of Experts review on any artifact — code, architecture, plans, repos, or documentation
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Invoke a Panel of Experts review on any artifact — code, architecture, plans, repos, or documentation
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Registry and index of all orchestration command skills
Aggregates session data from every project slug in ~/.claude/projects/ and surfaces systemic process patterns that appear in 3+ different projects, producing a prioritized finding list with project count, example evidence, and recommended fixes
Multi-persona expert panel framework for critical analysis, refinement, and creative insight
Automatically mines Claude session JSONL and EVOKORE session data to compute efficiency metrics and produce a structured retrospective report with specific narrative improvement recommendations
Core orchestration framework for model-agnostic multi-agent workflows with handoff protocol, policy governance, and configuration schemas
| name | orch-panel |
| description | Invoke a Panel of Experts review on any artifact — code, architecture, plans, repos, or documentation |
| aliases | ["panel","expert-review","panel-review","experts"] |
| category | Orchestration Framework |
| tags | ["panel","experts","review","multi-perspective","quality","refinement"] |
| version | 1.0.0 |
| requires | ["panel-of-experts"] |
| metadata | {"source":"evokore","original_command":"orch-panel"} |
| resolutionHints | ["run an expert panel","get expert review","panel of experts","multi-perspective analysis","critical review with experts"] |
Invoke a Panel of Experts review on any artifact. Assembles virtual expert personas with defined backgrounds, biases, and domain expertise to provide multi-perspective critical analysis that generic review misses.
orch-panel <panel-type> <artifact> [options]
| Panel | Use For |
|---|---|
code | Code quality, patterns, bugs, refactoring |
repo | External repo evaluation, content review, integration plans |
re | Reverse engineering, binary triage, semantic recovery, debugger planning |
arch | Architecture decisions, phase plans, strategic direction |
security | Security review, threat modeling, compliance |
perf | Performance analysis, scaling, operational readiness |
dx | Developer experience, API design, tooling ergonomics |
test | Test strategy, coverage quality, resilience |
docs | Documentation accuracy, completeness, usability |
| Option | Description | Default |
|---|---|---|
--quick | Skip challenge phase (solo + converge only) | false |
--no-feasibility | Skip feasibility gate | false |
--cascade <panels> | Run multiple panels sequentially | — |
--mode <mode> | Panel-specific mode (e.g., pre-ingestion, phase-plan) | auto |
orch-panel code src/SessionIsolation.ts
Context: Multi-tenant session isolation layer. In the hot path for every
tool call. Concerned about TTL check performance and LRU eviction correctness.
orch-panel security --quick src/auth/OAuthProvider.ts
Context: OAuth JWT validation for HTTP transport.
orch-panel --cascade arch,code,security docs/ECC-INTEGRATION-PLAN.md
Context: 9-phase integration plan. Want architecture review first,
then code feasibility, then security assessment. Unified feasibility at end.
orch-panel repo --mode post-ingestion docs/ECC-INTEGRATION-PLAN.md
Context: This plan was generated from research agents analyzing an
upstream reference repo against our own codebase.
Review for accuracy, completeness, and integration quality.
orch-panel re --mode unknown-binary-onboarding samples\payload.dll
Context: Need a binary map, initial hypotheses, and a debugger plan.
Target may be packed and the first session must stay evidence-first.
orch-panel arch --mode decision
Decision: Replace imperative PluginManager.register() with declarative
plugin.json manifest loading.
Options considered:
1. Keep imperative (current)
2. Add declarative alongside imperative (hybrid)
3. Full migration to declarative only
Constraints: Must maintain backward compatibility with existing plugins.
When invoked, orch-panel:
panel-of-experts/panels/panel-of-experts/expert-roster.md--quick)--no-feasibility)For --cascade mode, executes multiple panels sequentially, with each panel receiving prior panels' findings as context, followed by a unified feasibility assessment.
| Input | Type | Required | Description |
|---|---|---|---|
| panel_type | string | yes | Which panel to convene |
| artifact | string | yes | What to review (file path, description, or inline) |
| context | string | no | Additional context, constraints, concerns |
| mode | string | no | Panel-specific mode override |
| Output | Type | Description |
|---|---|---|
| Panel Report | markdown | Full review with solo reviews, challenges, convergence, feasibility |
| Remediation Plan | list | Prioritized, actionable fix list |
| Risk Register | table | Identified risks with severity and mitigation |
| Dissent Log | list | Minority expert opinions that went against consensus |
panel, expert-review, expertsorch-panel code as part of standard code revieworch-panel arch as part of planning workflow