prlisted

# Pull request preparation ## Purpose Open one evidence-grounded pull request when ready. `verify` owns `branch-ready`; this skill owns `pr-body-ready` and `pr-open-ready` and has no downstream continuation. ## When to use Use after `verify`, or for a nearly ready direct PR request. ## When not to use Do not implement, review, verify, settle lifecycle state, merge, release, or fabricate evidence. ## Project-local evidence Public skills operate in customer-project mode by default. Use project-local artifacts when present, including `docs/workflows.md`. Do not require RigorLoop repository-internal specs, docs, reports, or governance files. Use portable defaults where safe and block on ambiguity. ## Inputs to read Resolve repository, remote, branches, verification evidence, handoff, tree, diff, and matching PR. Never summarize from memory. An explicit change ID, workflow change identity, owning-change field, or governed pointer is a signal even when invalid. governed signal: `no-governed-signal`, `single-governed-candidate`, or `invalid-or-ambiguous-governed-signal`. Only the first uses `PR0-portable`; the second loads `PR1-governed`; malformed, stale, conflicting, duplicated, unsafe, escaped, or ambiguous signals stop without portable fallback. Loading grants no authority. ## Closed classifications Classify each independent axis exactly. Unknown values fail before consistency checks. - submission intent: `open`, `draft`, `prepare-only`; - refresh authority: `none`