Issue To PR

Guide one GitHub issue through delivery without making the user remember the workflow. Treat GitHub and Git as the durable state, recommend exactly one next phase, and wait for explicit authorization before starting that phase.

Remain a coordinator. Delegate specialized work to the existing skills named below instead of restating or reimplementing their procedures.

Dependency Contract

Resolve skills by name from the skills available in the current session, regardless of whether they are user-level or repository-local:

• grilling for requirements interrogation
• refine-issue-plan for the one-time parent planning decision and any subissue creation
• report-implementation for the final acceptance-criteria, review, and verification gate for the current issue
• creating-pull-requests for PR preparation, approval, push, creation, and base routing

Before delegating any workflow phase, confirm all four direct dependencies are available. If any are missing, stop and name them. Do not improvise a replacement workflow or assume a filesystem path.

Do not call split-issue-into-subissues directly; refine-issue-plan owns that decision and dependency. Do not call review-implementation separately; report-implementation owns the review gate, invokes that skill at most once when available, and uses its standalone base gate otherwise.