research-web
User request: $ARGUMENTS
Comprehensive multi-wave web research. Strategically selects sources, evaluates credibility, cross-references findings, and synthesizes actionable recommendations.
Research log: /tmp/research-web-{YYYYMMDD-HHMMSS}-{topic-kebab-case}.md - external memory for all findings.
Phase 1: Research Planning
1.1 Parse Request
Extract from $ARGUMENTS:
- Primary question: What are we trying to learn?
- Context: Why do we need this? What decision does it inform?
- Constraints: Version requirements, platform limitations, etc.
If vague or empty: Ask user to clarify the specific question.
1.2 Create Research Log
More from doodledood/codex-workflow
review-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.
19review-simplicity
Audit code for over-engineering, premature optimization, and cognitive complexity. Identifies unnecessary abstractions, YAGNI violations, and overly complex solutions. Read-only analysis. Triggers: review simplicity, over-engineering, complexity check, YAGNI.
19