Compliance Review Report
Background & Use Cases
If your system involves sensitive domains such as payments, finance, or user privacy, the requirements specification must undergo compliance review to ensure no red lines are crossed. This skill scans your PRD across four dimensions to identify potential compliance risk points, preventing post-launch regulatory shutdowns or security incidents.
Input & Output
You need to provide: A confirmed requirements specification (including 4A constraint descriptions).
You will receive: A compliance review report covering four dimensions: data security (how sensitive data is stored, who can view it), financial security (whether transaction flows have gaps), business compliance (whether industry regulatory requirements are met), and technical compliance (whether APIs and data transmission are compliant). Each issue is annotated with severity level and improvement recommendations.
Process Overview
The Agent scans your requirements specification across four dimensions: data security (where sensitive data is stored, who can access it), financial security (gaps in transaction flows), business compliance (alignment with industry regulations), and technical compliance (API and data transmission compliance). Each issue is annotated with severity and improvement recommendations, and the final output is an integrated review report.