workflow-extendlisted

Captures a mid-PR sub-idea and implements it on the same branch as the existing PR — skips Phase 1 (Branch), preserves Verify → Review → Deliver, and uses workflow-commit-and-pr to update existing PR. Never creates a new branch or new PR.
lugassawan/swe-workbench · ★ 2 · Code & Development · score 71

Install: claude install-skill lugassawan/swe-workbench

Announce at start: "Using `swe-workbench:workflow-extend` — capturing and implementing sub-idea onto the existing PR." ## When to invoke - `/swe-workbench:extend` command - "extend the PR", "add this on top of the current PR" - Mid-PR follow-on idea surfaces while working on an in-flight branch - Related sub-idea that belongs on the same branch and same PR ## When NOT to invoke - No open PR exists for the current branch → command body owns the fallback (AskUserQuestion) - Sub-idea is unrelated to current PR → use `/swe-workbench:implement` for a fresh branch - PR is already merged → use `/swe-workbench:implement` for a follow-up PR - Bug on someone else's PR → use `/swe-workbench:debug` ## Precondition The command body detects the open PR before activating this skill and passes: - `PR_NUM` — open PR number - `HEAD_REF` — current branch name - `PR_URL` — URL of the existing open PR - `IS_DRAFT` — `"true"` if the PR is a draft, `"false"` otherwise (always lowercase) If PR_NUM, HEAD_REF, or PR_URL are absent, **fail loudly**: "workflow-extend requires an open PR on the current branch. Run `gh pr view` to diagnose or use the command-level fallback." If `IS_DRAFT` is absent, treat as non-draft and log a warning. ## Phase A — Capture (inline; no top-level issue by default) Apply the four lenses with brevity. Use `agents/product-manager.md` lens phrasing as canonical reference — do NOT invoke the product-manager agent (its filing-centric contract is wrong here). 1. **Probl