agent-grounding-reviewer

To identify grounding risks in a feature spec, compare the proposed specification against the project's existing technical context and features. This process surfaces technical impossibilities, overlapping functionality, and missing dependencies with concrete supporting evidence before implementation begins.

A grounding review is a structured analysis that examines a feature spec for backend SaaS feasibility, architecture constraints, and integration risks. It distinguishes blocking issues from advisory concerns, providing severity levels, evidence, and actionable mitigation recommendations to prevent rework.

You can check a feature spec for missing dependencies and overlapping features by running an automated grounding review against the project context. This comparison flags inconsistencies and unrealistic assumptions, categorizing them by severity with concrete evidence and actionable steps.

Yes, you can validate backend SaaS feasibility before design by analyzing the spec against technical context. The review scopes architecture and integration constraints, returning a structured report that flags blocking issues with concrete evidence and actionable mitigation recommendations.

The best way to prevent spec rework is to perform a rigorous grounding review prior to design and implementation. By comparing the spec against project context, you surface technical impossibilities and missing dependencies early, generating a prioritized list of actionable recommendations.

You should run a spec grounding risk assessment after drafting the feature spec but before design and implementation. Analyzing the spec against the technical context at this stage surfaces blocking architecture and SaaS feasibility issues, saving significant rework costs later.