stage-2-gap-analysis

To map raw product ideas to app archetypes for gap analysis, you process Stage 1 inputs to identify archetype matches with confidence scoring and run an A-N mechanism gap scan to reduce ambiguity.

An A-N mechanism gap scan evaluates raw ideas across all A-N mechanism categories to identify missing functional components, generating adaptive questions to fill those gaps and produce a complete scope contract.

You generate a scope contract from unstructured product ideas by matching inputs to app archetypes, applying targeted questions to resolve mechanism gaps, and consolidating the results into a combined raw artifact for downstream planning.

You need to prepare a Stage 3 handoff artifact when Stage 1 raw ideas require archetype matching and gap filling to achieve a completeness score that ensures auditable downstream planning and scope definition.

Performing gap analysis without a complete Stage 1 input triggers adaptive question generation designed to fill identified A-N mechanism gaps, allowing you to iteratively build a complete combined raw artifact.

The best way to reduce ambiguity in early stage product ideas is to map them to established app archetypes, perform an A-N mechanism gap scan, and apply targeted questions to construct an auditable scope contract.