namht-issueslisted

# namht-issues — plan / user stories → tracker issues The kit plans well and writes stories with real acceptance criteria, and then a human retypes them into Jira. This closes that gap: it reads the artifact `/namht-plan` or `/namht-user-story` already produced and creates the corresponding issues. **Creating issues is an outward-facing action** — other people get notified, and issues are awkward to delete cleanly. So this skill previews everything and **never creates without an explicit yes**. Its default mode writes a file, not a ticket. ## Inputs - **The source** — a path to a `namht-sessions/{plans,user-stories}/…md`, a story id, or pasted text. If nothing is named, Glob those folders and offer the most recent; never invent stories. - **The target** — where the issues go. **Always confirm this explicitly**, even if only one option exists. Never infer it from the git remote alone: the current repo is often *not* where the backlog lives, and creating issues in the wrong project is the expensive mistake here. - **Mode** — `preview` (default, writes a file only) or `create` (actually creates them). `--create` anywhere in the arguments signals the *intent* to create after the preview. It is **not itself the yes** — step 5 still shows the full set and waits for one. ## Providers — use whatever is connected, in this order 1. **A connected tracker MCP** (`mcp__*jira*`, `mcp__*linear*`, `mcp__*atlassian*`, …) — preferred: it knows the project's real fields, issue