validate-change-plan

Validate Change Plan

Use only the eight tools in the core profile. Do not present this workflow as equivalent to the full profile's PRD validator, security gates, or semantic-diff verifier.

Workflow

1. Break the plan into falsifiable claims: files exist, symbols exist, dependency directions are correct, named boundaries match communities or processes, and the stated blast radius is plausible.
2. Call health_check, then build or refresh the graph with analyze_codebase. Reuse the returned graph_path.
3. Resolve each named symbol with search_codebase, then verify it with get_symbol or get_context. Mark ambiguous or missing names as unverified instead of choosing a convenient match.
4. Call get_impact for every symbol the plan changes. Compare callers, importers, users, implementors, communities, and processes with the plan's scope claims.
5. If a real diff exists, call detect_changes and compare its affected symbols and risk scores with the plan. Skip this step for a plan-only review.
6. Call query_graph with graph="missed". Inspect flagged files or ranges before accepting any absence-based claim.
7. Use read-only query_graph queries for remaining structural assertions, adding ORDER BY when paging.

Verdict

Return one row per plan claim with the evidence, a verdict of supported, contradicted, or unverified, and the smallest correction needed. End with coverage gaps, unresolved questions, likely tests, and the plan steps that require deeper semantic or runtime validation.