req-investigate

Identify compliance risks in a design document by extracting gaps and unknowns, then using WebSearch to examine external terms and API constraints. This process produces a structured Markdown report with findings and client-facing follow-up items.

Investigate external API constraints by running an end-to-end review that uses WebSearch to scan policies and terms. It surfaces issues like "terms check required" and outputs a consolidated report named 07.investigation-report.md.

Generate a client-ready investigation report by providing your requirements document to an automated investigator that extracts ambiguities, gathers regulatory evidence, and prepares structured follow-up items in Markdown format.

Yes, you can use automated WebSearch to perform regulatory due diligence by scanning external terms, policies, and API constraints. It consolidates the evidence into a report with clear follow-up actions for clients.

Requirement investigation works without manual review by automatically using WebSearch to examine external terms and API constraints. It extracts gaps from the input design and generates a structured Markdown report with findings.

You need to run an investigation report when a requirements document contains ambiguities like "needs review" or "terms check required." It surfaces these issues and delivers a structured Markdown report with client follow-ups.