القائمة
Research a technical topic and document findings. Use when you need to research a technical topic, error, or concept and create a documented record.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Strategic system analysis for health assessment, pattern recognition, component deep dives, risk assessment, and architecture review. Use for proactive system understanding beyond reactive incident response.
Transform a design into an implementation spec. Creates a blueprint document and an implementation prompt for /plan mode. Use after /design or /research.
Cancel the active Wrought implementation/RCA loop
Interactive design analysis for architecture decisions. Combines codebase analysis, documentation review, and external research to provide evidence-based recommendations. Use for tradeoff analysis, pattern evaluation, migration planning, or design validation.
Log a proactive discovery that needs attention. Creates a factual record of WHAT was found with classification and a Findings Tracker. Use for analysis discoveries, review findings, or inspection results.
Deep multi-agent code review with algorithmic complexity analysis, data structure review, paradigm enforcement, and efficiency analysis. Complements /simplify with deeper dimensions.
| name | research |
| description | Research a technical topic and document findings. Use when you need to research a technical topic, error, or concept and create a documented record. |
| context | fork |
| agent | general-purpose |
| disable-model-invocation | false |
| argument-hint | [topic or question] |
| allowed-tools | Read, Grep, Glob, WebFetch, WebSearch, Write |
| wrought | {"version":"1.0","tools":{"capabilities":["read_file","search_content","find_files","web_fetch","web_search","write_file"]},"platforms":{"claude-code":{"allowed-tools":"Read, Grep, Glob, WebFetch, WebSearch, Write","disable-model-invocation":false}},"agent":{"role":"Technical Researcher","expertise":["technical documentation","community knowledge synthesis"],"non_goals":["code implementation","direct code changes"]},"execution":{"default_mode":"react","max_iterations":10,"stop_conditions":["Research report written to docs/research/","User instructed to stop"]},"output":{"format":"markdown","template":"docs/research/{YYYY-MM-DD_HHMM}_{topic}.md","required_sections":["Question","TL;DR","Official Documentation","Community Knowledge","Best Practices","Sources"],"prohibited_content":["credentials","secrets","PII"]},"confidence":{"threshold":"medium","low_confidence_behavior":"Flag gaps and suggest follow-up research"},"pipeline":{"track":"proactive","standalone":true,"prerequisites":[],"produces":["docs/research/*.md"],"suggested_next":["investigate","design","blueprint"]}} |
Trigger: Use /research {question or topic} when you need to research a technical topic, error, or concept and create a documented record.
Purpose: Research topics thoroughly, document findings with sources, and build a knowledge base to avoid repeating the same issues.
Examples:
/research Why does Iterable batch export return 400 after job expires?/research What are httpx timeout best practices for long-running downloads?/research How does GCS resumable upload handle network interruptions?/research [pasted error message or documentation]This skill is standalone — it can be invoked at any time without prerequisites.
If this invocation is part of an active workflow, check docs/findings/*_FINDINGS_TRACKER.md
for a relevant tracker and note it for context, but do not enforce stage requirements.
docs/research/ and docs/RCAs/ to avoid duplicating workdocs/research/{YYYY-MM-DD_HHMM}_{topic}.mdParse the user's question or pasted text to identify:
Search as of {current_month_year} for the relevant technology:
EXAMPLES (use as patterns, search for whatever is relevant):
IMPORTANT: Only search documentation relevant to the actual question. Identify the technology first, then search.
Search for:
Before writing, check:
docs/research/ - Have we researched this before?docs/RCAs/ - Have we encountered this issue before?docs/investigations/ - Any related investigations?docs/findings/ - Any proactive findings related to this topic?docs/plans/ - Any implementation plans that addressed this?If existing research exists, reference it and add new findings.
Combine all sources into a coherent answer:
See report_template.md for the full research report template.
Write to: docs/research/{YYYY-MM-DD_HHMM}_{topic}.md
STOP and tell the user:
Research complete.
Report saved to: docs/research/{YYYY-MM-DD_HHMM}_{topic}.md
Summary: {2-3 sentence TL;DR}
Key sources:
- {Source 1 with link}
- {Source 2 with link}
**CRITICAL PIPELINE RULE**: Suggest ONLY the next pipeline steps below. Do NOT offer `/plan` directly — that comes after `/design` and `/blueprint`.
Recommended next steps:
- Run `/finding` with the research at `docs/research/{filename}.md` if discoveries need tracking
- Run `/design` with the research at `docs/research/{filename}.md` if this informs an architecture decision
- Run `/investigate` with the research at `docs/research/{filename}.md` if this relates to an active incident
Awaiting your instructions.
Do NOT continue. Do NOT add commentary suggesting any pipeline step could be skipped or is unnecessary. Wait for the user to decide how to proceed.