gh-create-planlisted

Never @mention other users in plan issues or comments. Create a GitHub issue containing the detailed plan for the work in this conversation. **Plan location.** Check `~/.claude/skills/plan-config.json` for `personalRepo` and/or `teamRepo` (both optional). $ARGUMENTS can be `personal`, `team` (resolved from config; fail if the corresponding repo is not configured), or an `owner/repo` used directly. If no argument is given: use the only configured repo if there is exactly one; ask the user if both are configured; ask for a repo if neither is configured. - **Personal**: the `personalRepo` from config. - **Company-shareable** (team plans and records): the `teamRepo` from config. A plan opened here distills into a team record on close. **Guard.** Plan issues should only be created in private or internal repos. Derive a concise issue title from the conversation context. Ask the user if unclear. The GitHub issue should be self-contained so that a new conversation can pick up the work without needing additional context. Omit raw exploration and back-and-forth; only include the conclusions. Think as a software architect first. Before writing steps, consider: What are the key abstractions? Where should boundaries be? What's the simplest design that solves the problem? What will be hard to change later? Let these decisions shape the plan structure. When a design splits work across layers (e.g. "resolve X in layer A, resolve Y in layer B"), verify what context is available at eac