19 lines
1.1 KiB
Markdown
19 lines
1.1 KiB
Markdown
---
|
|
name: technical-research
|
|
description: Use before implementation when an unfamiliar or changing technology, API, standard, or technical trade-off needs current evidence. Prefer primary sources; do not use for repository-only code discovery.
|
|
---
|
|
|
|
# Technical Research
|
|
|
|
Use before implementation when an unfamiliar technology, API, current product behavior, or technical trade-off could change the solution.
|
|
|
|
## Workflow
|
|
|
|
1. Turn the implementation question into specific facts or decisions that need evidence.
|
|
2. Prefer current primary sources: official product documentation, standards, release notes, or the original research. Check version and date when behavior may have changed.
|
|
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.
|
|
|
|
Return concise findings with direct sources and an implementation-relevant conclusion. Do not implement the change.
|