design-verification

Design verification compares a design document against the actual codebase to identify schema conflicts, type mismatches, and pipeline assumptions before implementation. It surfaces blockers and misalignments across new pages, API routes, and UI changes by loading and analyzing the latest design context.

Design-to-code gap analysis is the process of comparing design specifications against your actual repository to surface misalignments and blockers. You need it before implementing new pages, API routes, or UI changes to ensure design feasibility and catch type mismatches early.

You run design verification with your latest design document to drive multi-agent verification across code, tests, and architecture. This workflow leverages repository access and tools like Read, Glob, Grep, and Task to ensure end-to-end feasibility checks and provide actionable remediation steps.

Yes, you need a .feature-flow.yml context, stack or platform references, and repository access to check design feasibility. The verification workflow requires these inputs to apply context-aware exploration, checks, and remediation workflows across your codebase.

The best way to catch type mismatches and pipeline assumptions before implementation is aligning your design document with the actual codebase through design verification. This provides actionable remediation steps and traceability back to design items for resolving blockers early.