i9wa4 Technical Research
Owns evidence-based investigation: verifying claims, comparing options with sourced tradeoffs, and confirming how libraries, APIs, and tools actually behave before conclusions are relied on.
1. Discipline
- Verify information from multiple sources before presenting as fact
- Prefer official documentation over blog posts; note publication dates
- Flag confidence level (High/Medium/Low) on each finding
- Clearly separate facts from opinions and recommendations
2. Workflow
Clarify scope: what exactly needs to be answered?
Search official docs first (WebSearch + WebFetch)
Check GitHub repos: issues, discussions, source code for implementation details
# Clone to /tmp for analysis when needed git clone --depth 1 <repo-url> /tmp/<repo-name>Cross-reference: do multiple sources agree? Flag contradictions.
Test when possible: run code, check versions, verify claims hands-on
When synthesis needs categories, labels, or first-use terms before final wording, use
clarify-conceptsafter evidence acquisition and before drafting conclusions.
3. Source Priority
- Official documentation and changelogs
- Source code and GitHub issues/discussions
- Well-maintained community resources
- Blog posts (note date, may be outdated)
4. Output Format