ship

STOP -- DO NOT READ THIS FILE. You are already reading it. This prompt was injected into your context by Claude Code's plugin system. Begin executing Step 1 immediately.

/pbr:ship -- Create PR from Planning Artifacts

References: @references/ui-brand.md

You are the orchestrator for /pbr:ship. This skill generates a rich pull request from PBR planning artifacts -- SUMMARY one-liners, verification status, and requirement coverage. It uses gh pr create to open the PR.

Step 0 -- Immediate Output

Before ANY tool calls, display this banner:

+--------------------------------------------------------------+
|  PLAN-BUILD-RUN > SHIP                                       |
+--------------------------------------------------------------+

Then proceed to Step 1.

Step 1: Parse Arguments and Validate

1. Parse $ARGUMENTS for optional flags:
   • --base <branch> -- target branch for the PR (default: repo default branch)
   • --draft -- create as draft PR
2. Verify gh CLI is available: gh --version
3. Verify git working tree is clean. If uncommitted changes exist, warn:

   WARNING: You have uncommitted changes. Commit or stash before shipping.
   

   CRITICAL -- DO NOT SKIP: Present the following choice to the user via AskUserQuestion before proceeding: Use AskUserQuestion (pattern: yes-no): question: "Continue with uncommitted changes?" If "No": stop.
4. Verify current branch is NOT the default branch:

   git rev-parse --abbrev-ref HEAD
   

   If on main/master, warn and stop: "You are on the default branch. Create a feature branch first."

Step 2: Gather Planning Artifacts

1. Read .planning/STATE.md to get current phase info (phase number, slug, status)
2. Find the current phase directory: .planning/phases/{NN}-{slug}/
3. Read all SUMMARY-*.md files in the phase directory:
   • Extract status from frontmatter
   • Extract one-liner descriptions from the body (first non-heading, non-empty line after ## Task Results)
   • Collect commits arrays from frontmatter
4. Read VERIFICATION.md in the phase directory (if exists):
   • Extract score and status from frontmatter
   • Extract pass/fail counts
5. Read .planning/ROADMAP.md:
   • Extract requirements mapped to the current phase
   • Extract phase goal
6. Compute git stats:

   git diff --stat $(git merge-base HEAD main)..HEAD
   git log --oneline $(git merge-base HEAD main)..HEAD | wc -l