Answer "is this ready" with the criteria the RHDH workflow actually enforces, and say what is missing rather than guessing at it.

Load . It covers both the per-issue readiness audit and the Feature Exploration checklist — the same checks, applied at different points in a Feature's life.

Unlike , this skill does not require the external skill and must not be blocked on it. Refinement reads work that already exists. Gating it on an optional external skill would take a whole capability offline for no benefit.

The report is read-only. When the user asks for fixes, each change becomes an external write: invoke and follow it. A refine pass typically proposes many small fixes at once, so state them as one set — issue key and exact command per row — rather than approving them one at a time.

Complete when every issue the report covers was actually fetched with its custom fields enriched — an unenriched search returns empty Story Points, Team, Size, and Sprint, which looks identical to a field nobody set and is the single most common source of a false "missing data" finding. Report the JQL, the issue count, and whether the result was truncated. Every finding names the check that produced it and its severity. A field that could not be retrieved is reported as unretrieved, never as missing.