القائمة
Multi-agent research orchestration for gathering technical, architectural, UX, security, and competitive insights. Use before brainstorm, during planning, or for troubleshooting.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Multi-agent consensus code review with adaptive budgets, complexity-aware agent selection, multiple consensus protocols (Approval/Veto, AAD, CI, Supermajority), cross-agent coverage tracking, context-folding isolation, and progressive summarization. Use when reviewing PRs, directories, or code changes.
Use when creating new repositories, reviewing existing repos for compliance, or enforcing repository naming, structure, documentation, and security standards. Applies to all fyrsmithlabs projects.
Use when releasing a new version of a fyrsmithlabs plugin. Automates version bumping across all manifests (plugin.json, marketplace.json, CLAUDE.md), validates counts match disk, runs plugin-validator, creates git tag and GitHub release. Say "release the plugin", "bump version", "create a release".
This skill should be used when the user asks to "test opa", "opa test", "test rego", "write rego tests", "policy coverage", "conftest verify", "mock opa", or mentions `_test.rego` files. Provides OPA testing framework guidance including unit tests, mocking, coverage, and Conftest patterns.
This skill should be used when the user asks about "opa cli", "opa eval", "opa build", "opa check", "opa fmt", "regal lint", "opa bundle", "opa bench", "opa run", or mentions OPA tooling, CI/CD pipeline integration for OPA, or Rego linting. Provides OPA CLI and ecosystem tooling reference.
This skill should be used when the user asks about "kubernetes policy", "gatekeeper", "constraint template", "terraform policy", "conftest", "terraform compliance", "docker policy", "dockerfile policy", "envoy authz", "envoy authorization", "service mesh policy", "cloud policy", "aws policy rego", "azure policy rego", "gcp policy rego", or mentions writing OPA policies for a specific platform. Provides platform-specific Rego patterns and input schemas.
| name | research:orchestration |
| description | Multi-agent research orchestration for gathering technical, architectural, UX, security, and competitive insights. Use before brainstorm, during planning, or for troubleshooting. |
| triggers | ["/research","research orchestration","gather research","before brainstorm research"] |
Execute parallel research agents to gather comprehensive insights on a topic, then synthesize into actionable reports.
This skill builds on shared orchestration patterns. See:
includes/orchestration/parallel-execution.md - Agent dispatch and concurrencyincludes/orchestration/result-synthesis.md - Collecting and merging resultsincludes/orchestration/context-management.md - Context folding and memoryincludes/orchestration/checkpoint-patterns.md - Save/resume workflowsThe patterns below are research-specific extensions.
Dispatch selected agents with:
After all agents complete:
| Query Contains | Agents to Dispatch |
|---|---|
| "how to implement" | technical, architectural |
| "best practice" | technical, security |
| "UI", "UX", "user" | technical, ux |
| "secure", "auth" | technical, security |
| "compare", "vs" | technical, competitive |
| "market", "trend" | competitive |
| Default | technical, architectural |
docs/.claude/research/{topic-slug}/
├── README.md # Executive summary
├── technical.md # Technical findings
├── architectural.md # Architecture analysis
├── ux.md # UX considerations (if applicable)
├── security.md # Security analysis (if applicable)
├── competitive.md # Market context (if applicable)
└── sources.md # All citations
ALL web searches MUST include current year:
WebSearch(query: "{topic} best practices 2026")
Every finding must include:
Every finding must cite:
/brainstorm "add feature X"
-> Automatically triggers /research "feature X" first
-> Brainstorm receives research context
Error encountered
-> /research:debug "error message"
-> Technical + architectural agents analyze
| Command | Agents | Use Case |
|---|---|---|
/research "topic" | Auto-selected | General research |
/research:quick "topic" | technical only | Fast answer |
/research --agents tech,security "topic" | Specified | Targeted |
/research:debug "error" | tech, arch | Troubleshooting |
After synthesis completes, run consensus review:
documentation-reviewer - Technical accuracy, completenesscode-quality-reviewer - Code example correctness (if applicable)| Requirement | Threshold |
|---|---|
| Consensus Score | >= 70% |
| Critical Findings | 0 |
| High Findings | 0 |
If consensus < 70% OR critical/high findings exist:
See includes/orchestration/consensus-review.md for detailed patterns.