research-workflowlisted

# Research Workflow ## Goal Run higher-stakes topics as resumable, tiered research threads outside the curated vault until they are ready to promote. ## Use When - The user wants a structured research run rather than an immediate vault answer. - A topic needs source collection, contrarian review, and a final report. - An external model report should be imported as a lead, not treated as authority. ## Core Flow 1. **Start a run**: `uv run kops research-start --topic "<text>" --tier <fast|standard|deep>`. 2. **Check status**: `uv run kops research-status [topic|all]`. 3. **Collect sources**: `uv run kops research-collect --agent <codex|claude|gemini> --topic "<topic>"` (runs collect prompt). 4. **Adversarial review**: `uv run kops research-review --agent <codex|claude|gemini> --topic "<topic>"` (runs review prompt). 5. **Draft report**: `uv run kops research-report --agent <codex|claude|gemini> --topic "<topic>"` (runs report prompt). 6. **Import external reports**: `uv run kops research-import --topic "<topic>" --path <file> --provider <provider> --origin <origin>`. 7. **Archive completed run**: `uv run kops research-archive --topic "<topic>"` (after phase shows `done`). ## Phase Guidance The `research-collect`, `research-review`, and `research-report` CLI subcommands render their own runtime prompts (from `kops/templates/`), so no separate skill is needed. When running or reviewing a phase by hand, hold to these contracts: - **Collect** (`research-collect`): populate the