spec-flow-analyzer

To find gaps in product specifications, you analyze feature descriptions by mapping user flows, entry points, and decision points to surface missing paths and ambiguous requirements. This process generates a concise gaps report with actionable, decision-ready questions.

Specification gap analysis is the process of walking through a feature spec as a user to identify missing flows, unhappy paths, and unspecified state transitions. It surfaces ambiguities before implementation begins, producing a structured flow map and clarifying questions.

You analyze user flows by mapping entry points, happy paths, and terminal states, then comparing these mapped flows against the original spec. This comparison detects missing paths, permission boundaries, and integration seams, resulting in formulated questions with rationale and default assumptions.

Yes, you can ground the analysis in your codebase by searching for existing constraints and patterns before evaluating the spec. This contextual grounding shapes the flow mapping and gap detection process to reflect actual technical limitations.

You need to run a gap analysis on feature specifications before implementation begins, when fixing missing flows and edge cases is cheapest. It is necessary whenever you have plans or feature descriptions across product areas that require validation against end-user requirements.

The best way to generate clarifying questions for ambiguous requirements is to map the user flows, identify specific gaps like unhappy paths and state transitions, and formulate concrete, decision-ready questions complete with rationale and default assumptions.