research-batch-processor

Batch processing research notes involves scanning markdown files in specified directories, analyzing each for classification and flags, and presenting an aggregated routing plan for single operator approval before execution.

Auto-aggregating research notes requires listing markdown files in research folders, running per-file analysis without execution, and generating a combined batch report with auto-execute and needs-review sections.

Yes, you can route a directory of markdown research notes by collecting per-file metrics across all files, presenting a combined batch report, and executing all eligible routing actions after a single operator approval.

Batch routing research notes explicitly skips README.md and inbox.md files while processing all other markdown files in the docs/research/ and docs/research/roadmap/ directories.

Reviewing research notes before execution happens through an aggregated batch report that separates files into auto-execute and needs-review sections, requiring operator approval before any routing actions proceed.

Batch routing research notes includes robust guardrails for safety and rollback within the end-to-end execution flow, ensuring operator control through a single approval gate before any actions are taken.