RHDH test-plan review

Compare the version tables and key dates a test-plan issue carries against what the lifecycle sources and the release schedule actually say, then apply what the user accepts.

Read first. Nothing reaches Jira until the user has walked the diff row by row and approved a stated set of writes.

Route

1. Resolve the plan key or URL and the target RHDH version.
2. Load workflows/review-test-plan.md and follow it end to end.
3. Load references/sources.md at Step 4 — it holds every lifecycle URL and the extraction rules per product.
4. Load references/google-sheets-setup.md only when schedule access fails.

Named-skill handoffs