Create pull request

Position

Final delivery stage of the SDLC pipeline, after sdlc-execute-plan and normally after sdlc-validate-implementation. It consumes sdlc/<work-item>/pr-summary.md (kept current during execution) plus the branch's committed state, and produces one opened Azure DevOps pull request into the target branch. It does not implement, change requirements, or edit intent/spec/plan except to record the resulting PR link.

The pr-summary.md artifact

Each work item carries a reviewer-facing sdlc/<work-item>/pr-summary.md. It is distinct from plan.md's ## Handover (working state for resuming work): pr-summary.md is the narrative a reviewer reads on the PR. Its first line is the PR title; the rest is the PR description body. The source and target branches are not stored here — the workflow resolves them at creation time. The work item is linked through the create/update API call (--work-items, resolved from the <work-item> folder), not written as description text — an AB#<id> line in the body does not create the association.

# PR: <imperative title, ~50 chars, e.g. "Wire phoenix-one CI and integration tests">

## Summary
<1-3 sentences: what this delivers and why, tied to the intent's outcome>

## Changes
- <notable change, appended as tasks complete>