featureplanlisted

# /feature plan ## Instructions ### 1. Gather the idea If the user provided a description, use it. Otherwise ask: ``` 📋 Which feature do you want to plan? Describe briefly: - What should the feature do? - What problem does it solve? ``` ### 2. Gather external context **Auto-detect ticket from branch:** Run `git branch --show-current` and extract ticket IDs (pattern: `[A-Z]+-[0-9]+`). If a ticket ID is found: ``` 🔀 Branch: {branch-name} 🎫 Ticket detected: {TICKET-ID} Load the ticket? (y/n) ``` If yes → fetch via Jira API and show summary. **Then ask for additional sources:** ``` Any additional sources? 1. 🎫 Jira-Ticket(s) oder Epic(s) — Key(s) angeben (z.B. DEV-1234) 2. 🔴 Sentry-Issue(s) — URL(s) angeben (falls relevant) 3. 🔗 Andere Links — Confluence, Slack, Docs, etc. 4. ❌ No — start without additional sources ``` If the user provides ticket keys: - Fetch each ticket via Jira API (`/issue/{key}`). - For Epics: also fetch child issues (`/search/jql` with `"Epic Link" = {key}` or `parent = {key}`). - Extract and summarize: - **Title & description** — the original requirement - **Acceptance criteria** — if defined in the description or subtasks - **Comments** — relevant discussion, decisions, or clarifications - **Status & priority** — current state - **Linked issues** — related tickets, blockers, dependencies - **Subtasks / child issues** — for Epics, list all child tickets with status Show a structured summary: ``` 📋 Jira context loaded: {K