r2-req-module

Extracting module requirements from project specifications involves reading .r2mo/requirements/project.md and API metadata to generate structured module-level requirement documents following a fixed template structure.

Generating module-level requirement documents requires inputs including .r2mo/requirements/project.md, project-module.md templates, .r2mo/api/metadata.yaml, operations markdown files, schema files, and optionally proto definitions and design specs.

Documenting module requirements from API metadata and proto files involves parsing .r2mo/api/operations and .r2mo/domain/*.proto sources, then writing validated YAML headers and markdown content to src/pages/{module}/requirement.module.md.

Yes, you can use .r2mo/design/spec.md as an optional input for module requirement extraction alongside mandatory API operations and schema files to enrich the generated module specification documentation.

The best way to structure module requirement outputs is to place requirement.module.md and metadata.yaml under src/pages/{module}/ directories, enforcing strict YAML header validation and fixed template adherence.

Module requirement extraction requires strict YAML header validation to ensure generated specification documents conform to the fixed template structure, maintaining consistency across module configuration files and requirement markdown outputs.