pharaoh-reqs-from-module

To reverse-engineer requirements from multiple source files into a single document, you can orchestrate parallel per-file subagent dispatch to generate and aggregate comp_req directives into one cohesive RST file. This ensures consistent terminology and a unified view across the module.

Ensuring traceability and consistent terminology across a module with scattered comp_reqs requires orchestrating parallel per-file analysis and aggregating the results into a single RST document. This approach consolidates cohesive source directories into a unified output.

Generating comp_req directives for a Papyrus workspace module involves coordinating parallel dispatch across a specified module directory and file list. The process aggregates per-file results into a consolidated RST document for downstream consumption.

Yes, you can process multiple files simultaneously when reverse-engineering module requirements. The orchestration dispatches parallel subagents for each source file concurrently, ensuring fast and scalable analysis while preserving cross-file traceability.

Yes, consolidating RST documents from source code requires coordination with atomic skills like pharaoh-context-gather, pharaoh-req-from-code, and pharaoh-decision-record. The orchestrator relies on these atomics for actual generation while it handles the parallel dispatch and aggregation.