sm:stage:live-mirror

To find invisible decisions in a git diff, compare the original prompt or plan file against the produced code. This surfaces hidden assumptions, silent defaults, and unintended inventions introduced by the coding tool so you can review them before merging.

Spec vs. output comparison is the process of matching a development plan or prompt against a git diff or pull request. It systematically highlights mismatches, prioritizing architectural conflicts, default choices, and tradeoffs made during implementation.

To check architectural zones in a pull request, use reference mappings to inspect code areas against the original plan. This identifies unintended library choices, naming conventions, and error handling patterns not explicitly specified in the requirements.

Yes, you can use a prompt and a git diff to detect silent defaults. Comparing the explicit prompt instructions against the actual code changes reveals fallback behaviors and assumptions the coding tool invented without direct specification.

The best way to review unspecified library choices is to run a spec comparison against the session output. This generates a ranked report of invented decisions categorized by conflict, silent default, or reasonable fallback for you to accept or override.

You need to compare a specification against produced code during post-coding reviews and pull requests. This prevents hidden assumptions and divergences between your intent and the implementation from becoming permanent parts of the codebase.