pr-draftlisted

# /pr-draft — draft the PR Final step of the AI-DLC pipeline (after the building phase). Synthesizes a `pr.md` from the inception artifacts and the **actual work done** on the branch, ready to paste into a pull request. ## Input The story slug, e.g. `/pr-draft weather-tool`. Reads `.local/user-stories/<slug>/{story.md, design-doc.md, tasks/}` where present. If the slug is omitted, infer it from the branch and the commits on it, and say which story you inferred; if that's ambiguous, list the candidates under `.local/user-stories/` and ask. ## Steps 1. **Gather context:** - Read `story.md` (scope, DoD) and `design-doc.md` (architecture, ADRs) if present. - Read `tasks/README.md` to see what was in scope and each task's final status. - Inspect the real diff: `git status`, `git diff main...HEAD` (or the appropriate base), and `git log` on the branch. The PR describes **what actually changed**, not just what was planned — reconcile the two and note any divergence. 2. **Read the template** in `references/pr-template.md` (bundled). 3. **Draft `pr.md`:** - **Title** — imperative, matches the story's intent and the repo's commit style. - **Summary** — what this PR adds/changes and why it matters, in a few sentences. - **What's included** — the concrete deliverables (files/modules/ADRs), grouped logically. - **Testing** — the exact commands a reviewer runs to verify, and what passes. Run them before writing the numbers down; never carry counts over from a prev