sm:shape:find-holes

You can review a specification document to identify underspecified areas where coding tools will invent behavior without your intent. The process requires quoting exact passages, mapping invention zones, and prioritizing holes by impact to prevent downstream rework.

AI coding tools invent behavior when specification documents contain underspecified requirements lacking explicit intent. Identifying these invention zones by quoting exact passages reveals where the tool will make invisible decisions and fill holes with assumed behavior.

To prioritize spec gaps during a spec review, rank holes by immediacy and proximity to the animating intent using P1–P3 levels. This prioritized impact approach highlights which underspecified areas require immediate remediation before an agentic handoff.

Yes, you can apply gap analysis to architecture docs, prompts, MRDs, and rough specs preparing for agentic coding. The analysis identifies underspecified areas where tools will invent behavior, offering structured remediation options to fix P1 issues or skip them with explicit consequences.

To fix P1 spec holes after identifying invention zones, use the provided remediation path to resolve issues interactively. You can pick one hole to resolve, apply structured remediation options, or explicitly skip fixing with documented consequences.