19 lines
1.7 KiB
Markdown
19 lines
1.7 KiB
Markdown
---
|
|
name: technical-research
|
|
description: MUST use before EVERY external technology search or lookup, including documentation fetches, API and package queries, familiar technologies, and follow-up searches; also before relying on unverified external behavior or choosing technical options.
|
|
---
|
|
|
|
# Technical Research
|
|
|
|
Apply `research` and this skill before every external technology lookup, even when the topic or version was researched earlier. Reuse loaded instructions, but check scope and evidence for each lookup. Verify external technology before it shapes the solution.
|
|
|
|
## Workflow
|
|
|
|
1. Turn the question into specific facts or decisions that need evidence. When the question concerns how this repository already uses the technology, run `repository-research` first and research only what the code does not answer.
|
|
2. Open primary sources: official documentation, standards, release notes, or source code of the exact version in use. Check version and date when behavior may have changed. Search snippets and secondary summaries locate evidence; inspect the primary source before relying on its claims. If unavailable, report the gap and qualify the conclusion.
|
|
3. Compare only viable options against the user's constraints, compatibility needs, security properties, and maintenance cost.
|
|
4. Separate source-backed facts from interpretation. Record assumptions and any material evidence that is missing or conflicting.
|
|
5. Recommend an option only when evidence supports it. Explain the deciding trade-off briefly.
|
|
|
|
Finish only when sources support the answer or remaining gaps are explicit. Return concise findings with direct sources, applicable versions, and an implementation-relevant conclusion. Continue authorized implementation after resolving its research questions.
|