plan-feature-from-issuelisted

# Plan Feature — From Issue (internal) Convert a feature-request issue into the project's planning artifacts, keeping a clean issue → SPEC → PR(Closes #n) trace. Writes the SPEC's **product half** (same two-halves convention `design-feature` uses) and must satisfy capability closure before handing off — a thin issue does not get a shortcut around it. **This skill stops at the Product half.** It designs, then the unit goes to `review-spec` for an independent Product review; engineering planning is a different authority's turn. Composing `plan-feature-scaffold` in the same breath as the design it just wrote is the bypass this separation exists to close — the author of a Product half cannot be the one who decides it is ready to build on. ## When to use - The `plan-feature` router calls this when the input is a GitHub issue (or `--from-issue N`) that describes new product capability. If the issue is a **bug or tech-debt**, stop and route it: `triage-issue` to classify, then `plan-fix` + `execute-phase --fix`. This skill is for genuine features only. ## Step 0 — Discover the project (always first) Per the agent guide's **Workflow conventions** + **documentation map**, then read what THIS skill needs: the feature SPEC template, the roadmap, and the issue/PR templates (`.github/ISSUE_TEMPLATE/`, `.github/PULL_REQUEST_TEMPLATE.md`) so the SPEC mirrors the fields reviewers expect. Then read the issue (forge CLI per the project's Workflow conventions — examples use `gh`): ```