pre-implement-spec

To analyze a specification for gaps before coding, you review spec completeness against project requirements and historical lessons. This process identifies missing components and ensures all necessary elements are included prior to implementation.

Backward compatibility audit in specification analysis is the process of checking new feature specs against existing contracts to maintain system stability. It identifies potential breaking changes before any code is written, reducing integration risks.

You assess technical risks in a feature specification by performing a pre-implementation analysis to identify potential integration and technical issues. This involves checking the spec against backward compatibility contracts and project lessons to catch vulnerabilities early.

Yes, you need an AGENTS.md file to check specification readiness effectively. The analysis process requires access to these project guides to verify compliance, ensuring the specification aligns with established project standards before coding begins.

The best way to prevent issues before implementation starts is to conduct a thorough pre-implementation analysis of your specifications. This catches backward compatibility issues, evaluates risks, and identifies gaps to ensure quality and reduce potential project failures.

The limitation of pre-implementation spec analysis is that it relies entirely on the availability and accuracy of input files like spec documents, backward compatibility contracts, and project lessons, meaning it cannot detect issues stemming from undocumented behaviors.