decision-gap-scout

Identify unresolved decisions by scanning repo docs and notes to surface high-priority gaps in scope, architecture, integrations, data models, testing, and risk. This produces a prioritized list of critical questions that could derail implementation.

You need a gap analysis during pre-implementation planning to surface missing decisions affecting rollout and security. Scanning documentation extracts unresolved stakeholder questions and architectural gaps before development begins.

The best way to find missing decisions is scanning relevant repository docs to extract gaps in data models, integrations, and scope. This returns a compact, prioritized list of high-value unresolved items.

Yes, a repo scan surfaces stakeholder questions by extracting gaps in architecture, risk, and requirements from current documentation. It identifies missing decisions that materially affect project scope.

Scanning docs for missing decisions is limited to analyzing existing repository documentation and notes. It cannot invent new requirements but only exposes unresolved gaps in scope, integrations, and data models already referenced.