Ticket to Ready PR

Take one ticket from source-of-truth requirements to a focused pull request ready for human review. Preserve the user's existing work, refuse invented product decisions, and make the pull request prove what it implements.

Explicit invocation authorizes scoped repository edits, an isolated feature branch or worktree, tests, local commits, an ordinary push to that feature branch, draft pull-request creation, and conversion of that pull request to ready-for-review after the completion contract passes.

Invocation does not authorize merging, auto-merge, force-push, direct pushes to protected branches, production access or deployment, ticket status changes, ticket comments, customer communication, or unrelated cleanup.

Ready means ready for review

This skill produces a non-draft pull request that a human can review without first discovering missing requirements, obvious failures, unrelated changes, or dishonest test claims. It does not claim the pull request is merge-ready or shipped.

After the pull request enters human review, use Autopilot for conflicts, review threads, and later required-check failures. Use Ship Check for the independent pre-merge decision.

Preflight

Resolve before editing: