create-enhancement-issuelisted

Create one kind:enhancement GitHub issue against an EXISTING codebase — the lightweight single-issue analog of /deep-dive-feature (no interview, no doc-lock). Reads context read-only to draft a feature-shaped body, guards that the change needs NO contract/data-model edit (if it does, it's a feature — stop), confirms with the user, then creates it via create-enhancement.sh. Activate on '/create-enhancement-issue', 'create/file an enhancement issue for <x>', or 'enhance <existing behavior>'.
MartinKChen/harness-claude-code · ★ 0 · AI & Automation · score 72

Install: claude install-skill MartinKChen/harness-claude-code

# create-enhancement-issue Turn a one-off enhancement request into a single, ready-to-review GitHub issue that the `/ship` lifecycle can pick up and drive through `implement-slice.mjs` — the same cycle a feature slice runs (author E2E → implement → review → PR), without the `/deep-dive-feature` interview or PRD doc-lock. This skill is the enhancement-kind sibling of `create-feature-issues` (which decomposes a PRD into many slices) and `create-bug-issue` (Zone-A symptom only). An enhancement modifies an **existing** surface. The codebase already has its contracts, design system, and architecture docs, so this skill **reads** those for context but never changes them. The defining guard: **an enhancement never changes an API contract or data model** — if it would, it is a feature, and this skill stops and points you at `/deep-dive-feature`. ## When to activate - The user types `/create-enhancement-issue`, or phrases like "create / file an enhancement issue for <x>", "enhance <existing behavior>", "add <small change> to the existing <feature>". Do NOT activate to decompose a whole feature/PRD (that is `create-feature-issues`), to file a bug (that is `create-bug-issue`), or to drive implementation (that is `/ship`). ## Input A short description of the enhancement. If none was given, ask the user what they want to enhance before doing anything else. ## Workflow ### Step 0 — Resolve the repo `gh repo view --json nameWithOwner --jq .nameWithOwner`. If not a GitHub repo, sur