What problem does it solve? Writing a trustworthy PR description requires reconciling planning artifacts, Jira tickets, and the actual code diff — a tedious process where descriptions often drift from what the code really does or miss the rationale reviewers need. ## Core Features & Use Cases - Artifact-grounded drafting: Builds the PR title and body from .ai/<TICKET>/ artifacts (prd.md, decisions.md, investigation.md, backend-plan.md) with the real git diff as final authority on behavior. - PR history detection: Detects open or previously merged PRs for the branch/ticket via gh and proposes full, updated, or delta-only descriptions accordingly. - Review-gated publishing: Writes the draft to .ai/<TICKET>/pr.md for developer review and only pushes the branch and opens a draft PR on GitHub after explicit approval. - Use Case: After finishing implementation on branch PHG-418, ask for a PR draft; the skill reads the diff and artifacts, writes pr.md with a What & why / Changes body, and on your approval runs gh pr create --draft. ## Quick Start Ask the assistant to draft the PR for the current ticket branch, for example: draft the PR for PHG-418 against dev.