create-feature-issueslisted

# create-feature-issues Turn a locked-in feature into a set of release-safe **vertical slice** GitHub issues. Each slice becomes **one** issue whose body inlines its typed task breakdown (e2e / backend / frontend) as a **static-ID checklist** — there are no task sub-issues. The skill is always invoked with a `<feature-name>` that points at `docs/product-requirement-document/<feature-name>/` — there is no free-form / ad-hoc input path. It decomposes the work, quizzes the user for explicit approval, creates one issue per slice (with its branch), then **archives the spent PRD pair**. **The task checklist is the task ledger.** Inside each slice issue body, the `## Tasks` section is a checklist of static-ID entries (`e2e.1`, `be.1`, `fe.1`, …). Those IDs are **permanent keys** — they are never translated to issue numbers and never become their own issues. The fully-qualified permanent key is `s<slice#>.<type>.<n>` (the slice number comes from the slice issue); inside one slice body the short form (`e2e.1`) is unambiguous because the issue number already scopes it. The downstream workflow reads this checklist to know what to build, ticks each box on completion, and references the qualified key in commit trailers (`Task: s<slice#>.<id>`). Task-level dependencies are expressed in each entry's `blocked-by:` field as static IDs — not as GitHub `Blocked by` relationships. **The PRD pair is a single-use input.** `requirement.md` + `implement-detail.md` exist for exactly one purpose: t