doxa-research

Operate the Doxa Research CLI for approved research execution. Use only when the user explicitly says "use Doxa" or "Doxa Research", asks to run, resume, check, or cancel a Doxa job, or an established plan has already selected Doxa to execute `.prompt.md` files. Handles preflight, provider/mode selection, paid-run confirmation, background monitoring, and output/provenance capture. Do not trigger for generic deep-research or research-planning requests; guided-research owns framing and lineage, while this skill owns Doxa execution.

Process a known bug ID from a structured bug review into a revalidated fix plan and implementation path, including fix-worthiness, multiple-choice user decisions, architectural/common-pattern analysis, consistency and naming review, TDD regression tests, maintainability improvements, verification, tracker updates, and commit reporting. Use when Codex is given a specific bug ID and asked whether or how to fix it, or asked to proceed from a reviewed bug into a fix.

Structured multi-method process for reviewing code changes for bugs and maintainability risks, including test-suite evaluation, feature-specific probes, design-doc scope review, precise bug scope language, wrapper-aware validation, candidate validation with evidence, contract conflict handling, one-by-one user approval, regression tests, verified fixes, and bug-to-commit reporting. Use when Codex is asked to check for bugs, review recent work, review a component or project scope, validate suspected defects, or proceed from a bug review into fixes.