agent-grounding-reviewer

Analyzing feature specs for grounding issues involves comparing proposed designs against project context and codebase constraints. This process catches feasibility gaps, overlaps, and impossible claims early, outputting a structured review with blocking or advisory severities.

To conduct a spec review for technical feasibility, compare the feature design against project context and codebase constraints. This grounding process identifies feasibility gaps and overlaps, outputting a structured review with blocking or advisory severities to prevent misaligned designs.

Grounding in feature spec review is the process of validating a proposed design against the project's technical reality. It identifies contradictions, impossible claims, and overlaps by researching codebase constraints to ensure the spec is technically feasible.

You should run a grounding assessment during the plan or design phase before development begins. Reviewing the feature spec draft early ensures it aligns with current architecture and roadmaps, catching technical feasibility gaps before they cause misaligned designs.

Yes, a grounding review categorizes spec issues by severity, specifically using blocking and advisory levels. This severity categorization ensures development teams know which technical feasibility mismatches or contradictions must be resolved immediately versus those that are actionable suggestions.