Issue to Plan

Overview

Turn a finalized issue into a draft PR plus a single marked plan comment, then stop. The draft PR and its plan comment are the durable boundary between planning and execution.

Core principle: planning and execution happen in separate contexts. This skill never runs SDD or dispatches Task 1.

The plan lives in a PR comment, never the description. The description stays a concise, reviewer-facing summary (Closes #N + change summary + test plan): the simplest merge path — squash-merging from the GitHub web UI, which prefills the commit message from the PR body — then produces a clean commit message instead of a multi-kilobyte plan.

Entry Gate (all 6 steps, in order)

1. Run gh issue view <N> --json number,title,body,state.
2. If the title starts with [DRAFT], or the body's ## Brainstorm state section has a Next: line (a revision still in progress), stop and route to brainstorming-to-issue #<N>.
3. If the Size: value in ## Brainstorm state starts with quick task or small change, stop: say "Implement # directly, no plan — follow the build steps in its ## Brainstorm state." Do not claim, build, or plan here.
4. If the entire change is one file, one behavior, and one red-green-commit review pass, use superpowers:test-driven-development directly. Uncertainty means it is not trivial.
5. Claim the issue per repository rules: assign it and add the in-progress label.
6. Retain Closes #<N> for the PR description.