evaluate-plan

To evaluate plan coverage, compare the AI-generated implementation plan against its source PRD or spec to flag dropped features and misinterpreted intents, producing a structured traceability checklist of every requirement.

Gap analysis in product spec traceability is the process of identifying disparities between an implementation plan and source requirements, categorizing items as missing, partial, or misinterpreted to prevent dropped features.

Yes, you can evaluate plan gaps with an incomplete source document. The evaluation workflow includes source reconstruction capabilities to rebuild missing requirements before performing the coverage verification.

You generate a traceability report for user stories by providing the path to the source spec and the current plan, which triggers a deterministic evaluation workflow that outputs a structured checklist of every requirement with its coverage status.

Yes, the plan evaluation workflow supports design briefs. It applies to plan-review tasks across product specs, design briefs, and user stories to highlight dropped features and misunderstood intents.

The best way to classify misinterpreted requirements is using a structured gap taxonomy that categorizes every discrepancy between the plan and source PRD into missing, partial, or misinterpreted items within a coverage report.