pharaoh-req-from-code

To generate traceable requirements from C++ source code, you provide a single source file to reverse-engineer its observable behaviors into deterministic comp_req blocks. This process extracts what the code does without drafting architecture or plans.

Reverse-engineering code into comp_req blocks is the process of analyzing a single C++ file to identify observable behaviors and emitting requirements directives. It produces deterministic, single-file-to-many-req outputs for legacy code documentation.

You do not need a Papyrus workspace to extract requirements from a C++ file, as it is optional. Providing a Papyrus workspace path coordinates canonical terms and registers new concepts before naming them in the generated requirements.

You cannot derive requirements for an entire C++ project architecture at once, as the analysis is strictly limited to a single source file. It produces single-file-to-many-req outputs and explicitly avoids drafting architecture or plans.

To document observable behaviors in unfamiliar C++ codebases, you analyze individual source files to emit corresponding comp_req directives. This reverse-engineering workflow reduces manual spec drafting by focusing on deterministic, file-level behavior extraction.