pr-deliverylisted

# PR Delivery (PR Body and Review-Request Content) Write the **content (what)** of the artifacts that deliver completed changes: the PR title and body, and the review-request message. Perform **writing and judgment only**. Remain company- and platform-neutral. This is the final stage of the build process (... → development review → **create PR → request review**). The resulting PR later becomes input to another party's `pr-review`. ## Input (Provided by the Caller) - Changes (diff/commits), build context (problem solved, key design decisions, and verification evidence actually collected), and an optional linked issue or ticket. - A **Delivery Profile** that defines: - **Title convention:** for example, ticket-prefixed or plain. - **Body section set:** a subset selected from the Section Library below. - **Review-request policy:** `none` or `ask-once-then-send`. - Optional request type or review lens, such as standard, high precision, security, or performance. ## Delivery Profile (Caller-Injected) Apply the caller-provided profile without embedding environment-specific conventions in this skill. - Format the title according to the profile's title convention. - Include only the body sections selected by the profile, in the caller-specified order when provided. - For `none`, do not produce content intended for sending a review request unless the caller explicitly asks for draft-only content. - For `ask-once-then-send`, if approval was already obtained upstream, do no