create-issuelisted

# Create a GitHub issue (template-compliant, auto-seeded) ## What this does Turns a raw idea into an issue a future contributor can pick up cold: one self-contained **description** that obeys the project's issue template, then walks the idea from fuzzy to actionable — 1. **Brainstorm** — frames the problem, lays out 2-3 approaches with trade-offs, recommends one. 2. **Spec** — the formal design doc for the chosen approach. 3. **Implementation plan** — bite-sized, testable tasks an engineer (or `implement-issue`) can execute. Brainstorm, spec and plan follow the kit's own shared doctrine — [`../_shared/brainstorm-and-spec.md`](../_shared/brainstorm-and-spec.md) and [`../_shared/plan-shape.md`](../_shared/plan-shape.md) — so the artifacts match how the project plans work on every machine, with no third-party plugin installed (#324). **Large work does not leave here as one issue.** When the plan Step 6 writes would earn the profile's largest effort size, the idea files as a **parent plus tracer-bullet children** — the parent a plan-less tracking body `auto-dev` never dispatches, each child a vertical slice with its own plan and its blockers wired as native GitHub dependencies (Step 6's decompose branch; [`references/decomposition.md`](references/decomposition.md), the parent's body per [`references/tracking-issue.md`](references/tracking-issue.md)). `--no-split` keeps today's single large issue. **Everything lives in the issue body, not comments — deliberately.** GitHub's