gap-revealing-build

To identify missing requirements in a software architecture design, you can probe the design by attempting a partial implementation that stops at every ambiguity and generates a structured gap inventory. This validates technical feasibility and prevents building on under-specified designs.

Gap analysis in software prototyping is a structured discovery process that documents structural ambiguities by building skeleton implementations. You need it when you are unsure if a new architectural design is viable and must verify technical feasibility before full-scale development.

To validate a GitHub pull request design for technical feasibility, instruct the tool to probe the design at the specific pull request number. It will build scaffolding to verify clear parts compose while stubbing out ambiguous areas in a draft-only PR output.

No, this gap analysis approach does not require a fully specified design to start. It applies to design validation workflows by intentionally building skeleton implementations that stub out ambiguous areas, specifically designed to handle under-specified or ambiguous designs.

The limitation of using skeleton implementations for design validation is that the design must be reachable in the worktree. Additionally, it follows a strict draft-only PR output protocol, meaning it stops at ambiguities rather than completing the full feature build.