feedbacklisted

# Feedback Post user feedback as a GitHub issue in `ievo-ai/skills` so we can fix bugs, prioritize features, and improve the plugin. ## Step 0: Detect invocation context This skill has two flows: **(A) Generic feedback** — default. User invoked `/ievo:feedback` or expressed feedback intent freely. Go to Step 1. **(B) Skill-rejections feedback** — invoked from `/ievo:init` final feedback step (step 13 in v0.2.0+) with a list of skipped skills from the interview. The caller will provide context like: ``` The user just completed /ievo:init interview. They installed N skills and skipped these M skills: <list>. Collect reasons for the skips and submit as feedback to ievo-ai/skills, copying reasons forward as registry-improvement signal that can be relayed to vercel-labs/skills. ``` If invoked in flow (B), **skip Step 1** (type is implicitly "Idea" / registry-improvement) and **jump to Step 1b** below. Otherwise proceed with Step 1. ## Step 1: Classify the feedback type (flow A only) Ask the user using `AskUserQuestion`: - **Question:** `What kind of feedback?` - **Header:** `Type` - **Options** (single-select): - `Bug` — description: `Something broke or didn't work as expected.` - `Feature` — description: `A new capability you'd like to see.` - `Idea` — description: `General suggestion or design thought.` - `Question` — description: `You're stuck and want help / clarification.` Map to GitHub label: `bug` / `enhancement` / `idea` / `question`. ## Step 1b: Collect