request-evaluation

To perform gap analysis on a request, you submit the complex task for context decomposition. The system breaks down the request into action, subject, scope, constraints, and deliverables to surface ambiguities and generate a structured report.

Gap analysis is needed for project planning when requirements are incomplete, underspecified, or external context is missing. It detects implicit assumptions and critical gaps to enable precise scoping and reduce rework before execution begins.

You surface implicit assumptions in ambiguous requests by applying phase-based analysis. The system generates Bridged Assumptions and Critical Gaps, providing a ready-to-action verdict for informed decision-making and execution planning.

Yes, gap detection applies to multi-step, context-dependent tasks across domains. It decomposes context and analyzes deliverables to produce actionable guidance even when external context is missing or requirements are unclear.

The best way to reduce rework on complex initiatives with unclear requirements is pre-planning with structured gap detection. This process identifies missing context and acceptance criteria, producing a clear verdict for informed decision-making.

Automated gap analysis relies entirely on the provided request text for context decomposition. If the initial request lacks fundamental domain context, the resulting Bridged Assumptions and Critical Gaps may require significant manual verification before execution.