spec-sync-check

To automate discrepancy detection between code and specifications, run a sync check that compares implementation files against spec documents. This skill flags deviations in database schemas, API interfaces, and user flows by referencing specific spec sections.

Database schema divergences occur when implementation changes outpace documentation. This skill identifies these discrepancies by comparing code files like prisma/schema.prisma against corresponding markdown specification files to flag undocumented changes.

Specification-driven development compliance ensures implementation code accurately reflects intended design requirements. It involves automated discrepancy detection comparing code changes in data models, API interfaces, and user flows against defined specification files.

Yes, you can verify API interface changes automatically by running a sync check. This skill compares modifications in server actions and queries against interface specification documents, identifying and reporting specific areas of divergence.

The best way to maintain code sync is to trigger an automated discrepancy check after implementing new features. This verifies that new database fields, API endpoints, and user flows are correctly documented in corresponding specification files.

Yes, this specification sync check works with markdown spec files and Prisma schemas by directly comparing implementation code paths like src/queries/ and prisma/schema.prisma against defined specification documents to ensure adherence.