pre-implement-spec

To check a technical specification for backward compatibility, analyze it against 13 contract surface categories to identify breaking changes before development begins. This process audits API endpoints and module structures to ensure existing clients remain unaffected by new implementations.

Specification gap analysis is the process of pinpointing missing information crucial for implementation before coding starts. You need this pre-implementation assessment when preparing new API endpoints to verify that essential sections like error handling and data models are fully detailed.

To identify technical and integration risks in a software specification, perform a pre-implementation risk assessment using a comprehensive checklist. This evaluation detects dependency vulnerabilities and structural issues across contract surfaces, data handling, and security protocols.

Yes, you can verify API spec compliance by checking the technical specification against your project's AGENTS.md file. This ensures the proposed implementation adheres to established coding standards and best practices before any development work starts.

The best way to audit a spec for missing sections and security issues is to execute a completeness check covering contract surfaces, data handling, and UI conventions. This generates a detailed readiness report highlighting gaps and security risks proactively.

Pre-implementation specification analysis should not be used after development has already begun, as its purpose is to prevent costly rework proactively. It is ineffective for already deployed codebases requiring post-implementation code review rather than spec readiness evaluation.