web-research
User request: $ARGUMENTS
Conduct structured web research to gather external information, synthesize findings, and provide actionable recommendations.
Output file: /tmp/research-{YYYYMMDD-HHMMSS}-{topic-kebab-case}.md
Phase 1: Setup
1.1 Define Research Scope
Identify:
- Primary question: What are we trying to learn? (single clear question)
- Context: Why do we need this? What's the decision this informs?
- Success criteria: What would a good answer include?
- Scope boundary: What's explicitly NOT included in this research?
If $ARGUMENTS is vague: Ask user to clarify the primary question before proceeding.
1.2 Create Research Log
More from doodledood/codex-workflow
research-web
Comprehensive multi-wave web research with strategic source selection. Gathers information from official docs, community resources, and advanced sources. Use for deep technical research, API documentation, best practices. Triggers: research web, deep research, comprehensive research, find documentation.
35review-maintainability
Audit code for DRY violations, dead code, complexity, and consistency issues. Read-only analysis with actionable recommendations. Use before PR or for code quality review. Triggers: review maintainability, code quality, DRY, refactor review.
34review-bugs
Audit code for bugs, logic errors, race conditions, and edge cases. Read-only analysis producing actionable report. Use before PR, after implementation, or when debugging. Triggers: review bugs, find bugs, check for errors, code review.
29review-docs
Audit documentation accuracy against code changes. Identifies stale docs, incorrect examples, and missing documentation. Read-only analysis. Use before PR or after implementation. Triggers: review docs, check documentation, docs up to date.
21explore-codebase
Context-gathering for finding files to read. Maps codebase structure, returns overview + prioritized file list with line ranges. Thoroughness: quick for lookups, medium for bugs/features, thorough for multi-area, very-thorough for architecture audits. Triggers: explore, find files, where is, how does X work.
20review-testability
Audit code for testability design patterns. Identifies business logic entangled with IO, hard-coded dependencies, and mocking friction. Suggests functional core / imperative shell separation. Read-only analysis. Triggers: review testability, testable code, mocking issues, dependency injection.
19