create-issuelisted

Create a GitHub issue from a feature request or idea, with a full spec standard (Idea/Spec/AC/Files-To-Touch/Test-Plan/Out-of-Scope). Multi-repo. AGENTS.md in the repo overrides default templates. Multi-type system: --type=<code|research> flag plus auto-inference. Templates from references/issue-templates/<type>.md. Auto-injection of AGENTS.md ac_templates into the AC block plus 6-trigger issue-type detection (docs/epic/secret/mcp/live-ping/live-service). Codebase-memory auto-suggests files-to-touch and hotspots. Optional auto-handoff to /work-issue. Triggers: /create-issue, create issue, new issue, file issue, file feature, spec issue, idea as ticket.
Domek-Labs/stagecrew · ★ 0 · AI & Automation · score 66

Install: claude install-skill Domek-Labs/stagecrew

# /create-issue — Idea → specified GitHub issue **Type:** issue genesis / spec engineering ## Purpose Issue-genesis phase. A user idea becomes a fully-specified GitHub issue that `/work-issue` can pick up directly. The skill ensures every issue has Idea + Spec + AC + Files + Test-Plan + OoS before any code gets written. The spec standard matches what `/work-issue`'s Validator expects as a GO criterion — so no Validator STOPs on the first loop pass. ## Invocation variants ``` /create-issue "voice-diff review for the bot" /create-issue --type=research "benchmark ollama tool-use" /create-issue --repo your-org/your-repo "improve scheduler" /create-issue # → asks for idea + repo /create-issue --refine <num> [--repo <slug>] # → extend an existing issue with spec fields ``` **Argument parsing:** same as `/work-issue` (GitHub syntax, `--repo` flag, cwd fallback). **`--type=<code|research>` flag:** selects the issue template from `references/issue-templates/<type>.md`. If not set: auto-inference from user text (see the next section). ## Loop-type resolution In this order: 1. **Explicit flag** — `--type=<code|research>` 2. **Auto-inference from user text** (keyword heuristic) 3. **AGENTS.md `loop_types.default`** (fallback, typically `code`) 4. **Ambiguous input:** the skill asks explicitly "code loop or research loop?" ### Auto-inference keywords | Keywords in user text | Inferred type | |-----------------------|---------------| | "feat"