tasklisted

# Plan → Issues Convert a finished plan, PRD, or feature spec into one or more PR-sized GitHub issues using the project's `wade` infrastructure. > **Never use `gh issue create` directly.** Always use `wade task create`. > Using `gh` directly bypasses label enforcement, snapshot/diff detection, > and dependency analysis hooks. ## When to activate - The user asks to create **any** GitHub issue — a single bug, a single feature request, or a full plan/PRD breakdown - A plan or spec `.md` file has been written (or is finalized in conversation) - The user asks to "create issues from this plan" or "break this into issues" - After any planning session where the next step is GitHub issues > **Single issues are in scope.** Do not skip this skill just because there > is only one issue to create. The skill handles single-issue creation > (Step 1 assess → propose single issue → confirm → create) exactly like > multi-issue plans — it just skips the multi-issue steps. ## Step 1: Assess scope Read the plan and estimate the implementation size: - **Lines of code** — rough total across all files - **Number of concerns** — distinct areas (new endpoint, schema change, UI, tests, docs) - **File count** — how many files will be touched ### PR-size heuristics | Metric | Single issue | Multi-issue split | |--------|-------------|-------------------| | LOC | ~300–500 | >500 | | Concerns | 1–2 related | 3+ distinct areas | | Files | ≤10 | >10 across layers | | Review time | <1 hour | >1 ho