prd-sync-skill

To find gaps between product requirements and database schemas, you align PRD definitions with data models and code logic to expose missing or inconsistent requirements. This parallel auditing process surfaces logical mismatches that impede traceability across separate project artifacts.

Cross-domain traceability for product requirements is the process of mapping PRD definitions to database schemas and code implementations. It enables phase-based auditing to expose missing mappings and ensures logical consistency across isolated project artifacts.

Yes, you can audit code logic against a PRD when they exist in separate files. This Skill specifically applies to projects where PRD, data models, and implementation details exist in separate artifacts, enabling phase-based auditing and cross-domain traceability.

To generate a gap analysis report from PRD and code, run a parallel PRD-to-implementation audit by loading PRD.md, triggering the mapping agents, and producing a PRD_SYNC_REPORT artifact. You can update GAP_ANALYSIS.md or EXECUTION_PLAN.md to document findings and action items.

The best way to align documentation with code implementation is applying a phase-based workflow of Preparation, Parallel Auditing, and Synchronized Reporting. This disciplined analysis maps PRD definitions to code paths to surface gaps and produce traceability artifacts.

Yes, parallel auditing works for missing requirements mapping in data models by mapping PRD to data models and code paths simultaneously. This surfaces inconsistencies and missing mappings to produce a synchronized gap report documenting findings and action items.