plan-feature-from-issue

# 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. ## 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`): ```sh gh issue view <N> --json number,title,body,labels,state,comments ``` ## Process 1. **Classify first.** Confirm it is a feature. Not a feature if it describes a defect, regression, duplicated code, perf debt, or carries a "when to fix / trigger" clause → hand to `triage-issue`. State the verdict explicitly. 2. **Normalize language.** If not in the project's docs language (this rep...